Microservices Patterns¶
Richardson, C. (2018). Microservices Patterns: With Examples in Java. Manning.
Cited by¶
4 citations across 4 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Design Patterns
This sourceManning. Comprehensive 44-pattern catalog for microservices (Saga, CQRS, Event Sourcing, API Gateway, Service Discovery, Circuit Breaker).
- False Dilemma
- Product and engineering design — "should we build A or B?" suppresses smaller versions of both, hybrids, do-nothing, and reframings of the underlying need. Software architecture — "microservices or monolith," "SQL or NoSQL," which crowd out modular monoliths, polyglot persistence, and staged migrations.
This sourceCatalogs 44 patterns for service decomposition and monolith refactoring, treating monolith-versus-microservices as a design spectrum (including the modular monolith and staged migration) rather than a binary, supporting the software-architecture use.
- Product and engineering design — "should we build A or B?" suppresses smaller versions of both, hybrids, do-nothing, and reframings of the underlying need. Software architecture — "microservices or monolith," "SQL or NoSQL," which crowd out modular monoliths, polyglot persistence, and staged migrations.
Mechanisms¶
- API Gateway
- The gateway is a single point of failure
This sourceTreats the API gateway as the single entry point for external requests and notes that its unavailability blocks external access to backend services.
- The gateway is a single point of failure
- Transactional Outbox
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:266725f06cfd · see in the full table