Monolith First (2015)
Hahaha. I have been saying the same for years but have either been punished by my managers or mercilessly downvoted on HN.<p>Somehow mentioning that microservices might not be perfect solution in every case triggers a lot of people.<p>I have actually helped save at least one project in a huge bank which got rolled from 140 services into one. The team got also scaled down to third of its size but was able to work on this monolithic application way more efficiently. Also reliability, which was huge issue before the change, improved dramatically.<p>When I joined, I have observed 6 consecutive failed deployments. Each took entire week to prepare and entire weekend to execute (with something like 40 people on bridge call).<p>When I left I have observed 50 consecutive successful deployments, each requiring 1h to prepare (basically meeting to discuss and approve the change) and 2h of a single engineer to prepare and execute using automation.<p>Most projects absolutely don&#x27;t need microservices.<p>Breaking anything apart brings inefficiencies of having to manage multiple things. Your people now spend time managing applications rather than writing actual business logic. You have to have really mature process to bring those inefficiencies down.<p>If you want to &quot;do microservices&quot; you have to precisely know what kind of benefits you are after. Because the benefits better be higher than the costs or you are just sabotaging your project.<p>There are actually ways to manage huge monolithic application that don&#x27;t require each team to have their own repository, ci&#x2F;cd, binary, etc.<p>How do you think things like Excel or PhotoShop have been developed? It is certainly too large for a single team to handle.