Appendix B. Pattern Index
Exposing domain aggregates from a monolith to allow microservices to access entities managed by the monolith. |
|
Coexisting two implementations of the same functionality in the same codebase at the same time, allowing for a new implementation to be incrementally developed until it can replace the old implementation. |
|
Transmit changes made to an underlying datastore to other interested parties. |
|
Moving the source of truth from the monolith to a microservice. |
|
Using a dedicated database to provide read-only access to internal service data. |
|
A view is projected from an underlying database, allowing for parts of the database to be hidden. |
|
A facade service is placed in front of an existing shared database, allowing for services to migrate away from direct use of the database. |
|
Trigger functionality running in a separate microservice by sniffing requests sent to the monolith, and the responses that are sent back in return. |
|
A dedicated database to house all static reference data. This database can be accessed by multiple different services. |
|
Copy static reference data into microservice databases. |
|
Accessing data managed by the monolith via APIs rather than directly accessing ... |
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access