Database-per-Service Pattern
Each service owns its data store and exposes it only through its API — no other service reads its tables. This buys independent schema evolution and technology choice, at the cost of losing cross-service joins and ACID transactions that span services.
This Concept is waiting for its first lesson!
Each service owns its data store and exposes it only through its API — no other service reads its tables. This buys independent schema evolution and technology choice, at the cost of losing cross-service joins and ACID transactions that span services.
Are you a teacher? Sign in to start contributing.
Sign In