Technology RadarTechnology Radar


This item was not updated in last three versions of the Radar. Should it have appeared in one of the more recent editions, there is a good chance it remains pertinent. However, if the item dates back further, its relevance may have diminished and our current evaluation could vary. Regrettably, our capacity to consistently revisit items from past Radar editions is limited.

The microservice architecture enables the rapid, frequent and reliable delivery of large, complex applications. Additionally, it helps organizations to evolve their technology stack piece by piece.

Although Microservices should not be treated as the holy grail, they can make sense in certain situations for certain applications. Ideally, our approach these days is to go monolith first and extract parts that make sense to extract later. Otherwise, we see a "responsibility problem" when you start with Microservices from scratch without clear boundaries. If boundaries are not clearly defined, the whole architecture can quickly turn into a distributed big ball of mud which is something that needs to be avoided for obvious reasons.