mify

This! Can't agree more, I think we share the same idea, that's what the tool we're making is about: https://github.com/mify-io/mify/. It generates backend service code in a scalable way from the beginning, so that you wouldn't have to rewrite and move services to some other platform. It's better to have good architecture from the beginning, but I understand why people choose these platforms - they are saving a lot of time in the initial development, that helps them iterate quickly. What will happen next is that people spending time and resources to perform costly migrations, and some do this more that once.

Hello, for the past couple of months, we've been developing Mify and I wanted to share it with the people here. We've been writing backends for multiple different big and small companies and noticed that backend development progresses in way too similar cycles. At first people write a small set of services or in better case a single service to do what's needed. At some point the tech debt becomes too much of a hassle to handle as company grows, engineers are starting to scale the codebase, rewriting code, splitting monolith, introducing microservices and eventually after a bunch of iterations like that, people write some sort of in-house internal developer platform to quickly spin up services. The amount of effort it takes to go through this is really unnecessary. Every team needs to get a bunch of libraries for storage, configuration, lo