Introduction to Database per Service

Most of the patterns so far in this course deal with service code and the calls between services. This chapter deals with the data. The Database per Service pattern gives every service its own private data store. It is the default data rule for microservices, and this lesson explains why.

What the Pattern Says

The pattern is one rule. Each microservice owns exactly one data store. A data store is any database: relational, document, or key-value. The tables inside that store are private to the service. Every other service that needs the data must go through the owning service's API.