Building complex container-based architectures is not very different from programming in terms of applying design best practices and principles. The goal of this article is to present three popular extensibility architectural patterns from a developer’s perspective using well-known programming principles.

Let’s start with the Single Responsibility Principle. According to R. Martin, “A class should have only one reason to change.” But classes are abstractions used to simplify real-world problems and represent software components. Hence, a component should have only one reason to change over time. Software services and microservices in particular are also components (runtime components) and should have only one reason to change. Microservices are supposed to be a single deployable unit, meaning they are deployed independently of other components and can have as many instances as needed.

Leave a Reply

Your email address will not be published. Required fields are marked *