Grokking Microservices Design Patterns
Vote

0% completed

The Architecture of Database per Service

The rule is set: each service owns its data and hides it behind an API. This lesson covers the choices inside that rule. You will pick an isolation level, a database type for each service, and a plan for small lookup data that every service needs.

Three Levels of Isolation

You can apply the pattern at three levels. They run from weakest to strongest.

Level one: private tables or a private schema in one shared database server. A schema is a named group of tables inside one database. Each service gets its own schema, and its own login that can only see that schema

.....

.....

.....

Like the course? Get enrolled and start learning!