Why microservices will not solve your problems
<p>In the <a href="/blog/break_up_the_monolith_1/">previous post</a>, 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.</p>
Why microservices will not solve your problems
<p>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.</p>
Why it is not a replacement for distributed transactions
<p>The <a href="https://microservices.io/patterns/data/saga.html">Saga pattern</a> 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.</p>
Web site and blog. Writing about IT most of the time.
I'm Uwe, travelling the world of IT for many years. Worked in many roles in and around IT. Sharing my thought, ideas and insights here. Explorer. Connector. Sharer. Coder. Writer. Human. More. Order may vary.
Learn More
