<p>This post discusses two widespread fallacies – that microservices improve reusability (and thus pay for themselves after a short while) and that microservices improve team autonomy.</p>
<p>In the <a href="/blog/reusability_fallacy_3/">previous part of this series</a> I discussed why reusability is a false friend in distributed systems and thus should not be used to sell distributed architectural approaches. Additionally, I discussed the difference between “usable” and “reusable” assets and why you should strive for “usability” in distributed approaches like, e.g., microservices.</p>
<p>In the <a href="/blog/reusability_fallacy_2/">second part of this blog series about reusability</a> I discussed the costs of making a software asset reusable. It turned out that creating an actually reusable asset means multiple times the costs and efforts compared to creating the same asset just for a single purpose.</p>
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.