Microservices-based Architecture (MSA) Pattern

Context:
- It can (typically) breaks a Software Systems functionality into small, independently functioning service components.
- It can be enabled with an API-based Architecture.
- It can be a Data Layer-based MSA.
- It can be an Event-Driven MSA.
- …
Example(s):
- Amazon's MSA. [1].
- Netflix's MSA. [2].
- UBER's MSA. [3].
- …
Counter-Example(s):
- a Serverless Architecture.
- …
See: Protocol (Computing), Coupling (Computer Programming), Service Granularity Principle.

References

(Wikipedia, 2022) ⇒ https://en.wikipedia.org/wiki/Microservices Retrieved:2022-8-18.
- A microservice architecture – a variant of the SOA (service-oriented architecture) structural style – arranges an application as a collection of loosely-coupled services. In a microservices architecture, services are fine-grained and the protocols are lightweight. The goal is that teams can bring their services to life independent of others. Loose coupling reduces all types of dependencies and the complexities around it, as service developers do not need to care about the users of the service, they do not force their changes onto users of the service. Therefore it allows organizations developing software to grow fast and big, as well as use off-the-shelf services more easily. Communication requirements are reduced. These benefits come at a cost to maintaining the decoupling. Interfaces need to be designed carefully and treated as a public API. One technique that is used is having multiple interfaces on the same service, or multiple versions of the same service, so as to not disrupt existing users of the code.