|
- What are microservices?
Microservices - also known as the microservice architecture - is an architectural style that structures an application as a collection of loosely coupled services, which implement business capabilities The microservice architecture enables the continuous delivery deployment of large, complex applications It also enables an organization to evolve its technology stack
- Microservices Pattern: Microservice Architecture pattern
The microservice architecture structures an application as a set of loosely coupled, deployable executable components organized around business capabilities
- A pattern language for microservices
Architectural style Which architectural style should you choose for an application? Monolithic architecture - architect an application as a single deployable unit Microservice architecture - architect an application as a collection of independently deployable, loosely coupled services Service boundaries How to decompose an application into services? Decompose by business capability - define
- Microservices rules #8: Design independently deployable services
Microservices rules #8 is design independently deployable services Independently deployable service is a defining characteristic of the microservice architecture
- About the microservices rules: what good looks like
The 11 microservices rules are a great checklist that engineering leaders can use to assess the state of their organization, its delivery practices and its application’s architecture and keep their migration to microservices on track
- Pattern: Strangler application - Microservices
The Strangler Pattern is a design approach used to incrementally modernize a monolithic application by gradually replacing parts of it with microservices This pattern is particularly useful for organizations that aim to transition from legacy systems to a modern architecture without undertaking a complete rewrite of the application, which can be risky, time-consuming, and expensive Key
- Pattern: Transactional outbox - Microservices
First, write the message event to a database OUTBOX table as part of the transaction that updates business objects, and then publish it to a message broker
- Microservices platforms: when team topologies meets microservices . . .
The MEAP for Microservices Patterns 2nd edition is now available Team topologies and the microservice architecture have a synergistic relationship When developing application at scale, the microservice architecture enables the numerous stream-aligned teams to work independently
|
|
|