Isn’t backned mostly web2 tech, you may ask? While that’s partially correct, there are many tricky aspects when it comes to building backends for web3 apps: With the multitude of apps, of course…

Aishwary Gupta

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

This post discusses the challenges and considerations in building backends for web3 apps. It covers topics such as tight timelines and budget, caching for blockchain RPC calls, compliance with regulations, and safety in storing private keys. The post also recommends using NodeJS with TypeScript for backend development and explores the use of GraphQL Yoga and Nexus GraphQL. It suggests using Firebase for authentication and MetaKeep for account abstraction. The post further discusses KYC solutions in web3, image, and file storage options, and database choices. It concludes with insights on folder structure and code formatting, linting, and build tools. The post also mentions cloud deployment options such as GCP, AWS, and Railway.

Web3 Backend architecture that works