Top 6 Web3 MISTAKES (and how to avoid them)

Get the DevOps Roadmap for 2023 here: devopsfordevelopers.io/roadmap.
In this video, you will learn the top 6 mistakes developers make when building their web3 applications and how to prevent them. Please have a look at the chapter links below to jump directly to specific tasks. The lessons learned here apply to both professional web3 apps and portfolio projects.
If you learned something from the video, please give it a like and let me know in the comments what you learned!
----------🔗 L I N K S ----------
GitHub repository: github.com/WillButton/hodlers...
Thirdweb: thirdweb.com/
Polygon: www.polygon.technology/
Cloudflare Pages: pages.cloudflare.com/
Snyk: snyk.io/
----------🎥 C H A P T E R S ----------
0:00 Introduction
1:03 Deploy ERC-1155 Contract
6:08 Bootstrap our website
10:30 Writing tests
21:40 Setup GitHub Actions
28:30 Setup Snyk
34:50 Customizing our website
38:50 A professional README
45:09 Deploy to Mainnet
51:48 Deploy our production site
----------👋 C O N N E C T ----------
Discord ▻ devopsfordevelopers.io/discord
Twitter ▻ / 0xwillbutton
----------🛠 R E S O U R C E S ----------
The DevOps Career Guide ▻ devopsfordevelopers.io/devops...
DevOps Roadmap ▻ devopsfordevelopers.io/roadmap
DevOps merch ▻ devopsfordevelopers.io/merch

[@vitzcar6219]

Hey what do you think is the future of DevOps in Web3? Is it going to be the same as we do in web2?

[@DevOpsForDevelopers]

I, for one, welcome our new Overlords! errrr.... I mean, it's fine. 🤣
There are a lot of skills that transfer directly from Web2 to Web3. Most Web3 apps are very similar to the Single Page Apps (SPA) and Web Apps we've supported for years. Leveraging tools like CDN, optimizing JS, and using caching to improve build times will still set you up for success.
We must remember that most Web3 apps deal with financial transactions, so adequate testing is necessary to ensure we properly handle unexpected cases. This falls to the development team, but from a DevOps perspective, we act as the final checkpoint before rolling to production, so we need to look at this as well. To successfully accomplish this, we'll use mocking in our test suite because the transactions in question come from the blockchain network, which is slow. We don't want our tests to be dependent on external factors.
This also brings us to the next difference between Web2 and Web3: in a Web2 world, we often own the backend services used by our application. In a Web3 world, it's a global database (for lack of a better analogy). We need to ensure we're checking the availability of those services, monitoring them, and ensuring our development teams have graceful fallbacks in place for our users when they aren't available.
In advanced use cases, we may choose to host our own services to support our apps, which may mean building, deploying, and monitoring data aggregation services, running nodes for our given blockchain, or building new services that combine traditional data from databases and data retrieved from the blockchain.
A vital part of this success is architecting your application before building it, documenting it, identifying the failure points involved, and ensuring you've got monitoring and alerting around those points.
Web3 apps introduce wallets, signing transactions, and many other new requirements to work. A DevOps Engineer must be familiar with blockchain fundamentals such as signing transactions, tokens, and gas fees to support these apps.

[@vitzcar6219]

@@DevOpsForDevelopers Thank you for such a thoughtful answer. This channel is such a gem