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, logging, metrics, etc and duct tape them all together until it works, then write boilerplate for all of that, and then there's also infrastructure code and configs to set up deployment.

So, we think that it doesn't have to be that way and that's why we wrote Mify, which is an open-source tool that generated and maintains all boilerplate code for the necessary building blocks of a backend service and help with deployment. Even at this early stage Mify can save a lot of development time, so check it out, we would appreciate your feedback!