In the previous post, we started with the observation that companies (still) want to break up their monoliths into microservices. If you ask them what they expect from this measure, they typically expect to cure the “big ball of mud” issue with microservices or to improve their time to market with them.

Time and again clients approach my colleagues and me with the request that they want to break up their monolith into microservices and they ask us how to do this best. Apparently, they are convinced that breaking up the monolith into microservices will solve some big problems they had for a long time.

The Saga pattern has become quite popular in the context of microservices. While it basically is described correctly in the referenced source, most often I see a grave misunderstanding.

This post complements the discussion of the previous posts with a few general complementing recommendations and concludes this blog post series.

In this post we take a look at microliths as an alternative to microservices.