This document discusses the benefits of microservices architecture for maintainability. It argues that microservices help achieve maintainability through three main principles: 1) They allow individual services to be replaced independently without impacting the whole system, 2) They avoid redundant data and code by having separate data models and codebases for different bounded contexts, and 3) They promote independence between services which makes them easier to change and maintain separately. The document uses examples from e-commerce systems to illustrate how microservices can be organized by domain to achieve these principles of replaceability, avoidance of redundancy, and independence between teams and modules.
104. Open Source
> Good code quality
> Documentation
> Model to accept contributions
105. “But high quality Open Source is
hard.
We just share code!”
“You only provide high quality as
Open Source…
...but for colleagues low quality is
OK?”
106. Let’s assume it’s possible to reuse
code.
Reuse is still a tradeoff.