Microservices Are SOLID
Author: Matt Stine
Microservices are often described as small, loosely coupled applications that follow the UNIX philosophy of “doing one thing well.” They have also been related to the Single Responsibility Principle, the first of the five principles making up SOLID. A microservices-based architecture is typically constructed around a set of common patterns. This set of patterns is actually consistent with all of the SOLID principles when thought of at the architectural rather than the class/module level. In this article, we’ll gain an understanding of each of the SOLID principles and how they relate to microservices.
Single Responsibility Principle
Complecting responsibilities leads to rigid and/or fragile design.
Complecting concretions of an abstraction in such a way that new concretions adversely affect existing, working concretions is problemmatic.
Liskov Substitution Principle
Reuse via inheritance is dangerous. It often complects entities not in a true “is-a” relationship, which leads to non-substitutability.
Interface Segregation Principle
Don’t complect clients with uninteresting operations by complecting unrelated groups of operations in a single entity!
Dependency Inversion Principle
Transitive dependency leads to transitive complectedness!
Full article: mattstine.com/2014/06/30/microservices-are-solid