I've been in this industry since the days when monoliths (and dinosaurs) inhabited the planet and the JPEG format was still a child in the womb. As unpopular as it may sound, I grew up with multi-tier monoliths and, well, I’ve never lost that imprint and I've always been biased and skeptical of microservices. Fact is, microservices bring additional complexity that--in most cases--turn them into micro disservices with the value being outweighed by the sum of new problems and all cost items. I still see a lot of architectural similarity between monolithic and microservice architecture. A properly done monolith consists of watershed compartments that host highly cohesive modules. At the same time, coupling is low just because of said strong boundaries. This is the same argument you hear everywhere in favor of microservices. On the other hand, a poorly done microservice adds unnecessary and intrusive bureaucracy and ultimately results at the coarsest business level in both low coupling and low cohesion. Have you ever considered modular monoliths?


Get tickets to Build Stuff'24 here: https://www.buildstuff.events/tickets