Legacy systems
A different view on legacy systems
Last week I stumbled upon a nice quote from Corey Quinn that I shared via Twitter:
A different view on legacy systems
Last week I stumbled upon a nice quote from Corey Quinn that I shared via Twitter:
Why the reusability promise does not work
In the previous part of this series 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.
Why the reusability promise does not work
In the second part of this blog series about reusability 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.