Thread by @dipdup_io

🧵 Why you should try using DipDup indexing stack for your #dapp backend?
Reason number one: fast feature-to-market (1/7)

It is very easy to start building on DipDup, as it's #Python-based, accompanied with comprehensive docs and templates. You can also get help in our developer community. (2/7)

DipDup is a framework, and it gently guides you towards the right path by restricting file organisation, by providing to-be-implemented stubs, and other hints. (3/7)

DipDup significantly reduces boilerplate associated with querying and decoding data, handling network and blockchain issues. What left is just the core logic you need to implement. (4/7)

There's no need to re-implement common indexing blocks, such as #NFT metadata, #DEX quotes, etc — you can reuse existing services provided by DipDup Verticals (aka "indexing backends"). (5/7)

You can go further and split your backend into micro-services thus forming your own "Vertical". With such a design you can avoid re-syncing the entire system in case of a change, just the service that was updated and optionally its dependent services. (6/7)

Lastly (since we are dealing with micro-services) you are free to use any tech stack (currently #Python and @golang) to build Verticals, and delegate tasks to different teams, as long as the common indexing flow and communication interface are implemented. (7/7)