Does microservices use a common database?

Question

The use cases of using a shared database with microservices aren't common. An example could be a temporary state while migrating the monolith to microservices. The primary benefit of the shared database over per service is transaction management. There is no need to span the transactions over the services. 31 мар. 2022 г.

Do microservices need their own database?

As you described it very well above, each microservice needs to own it's DATA, which could be held within a dedicated database, within a dedicated schema (within a database), or even a set of dedicated tables (within a schema within a database).

I've seen folks refer to this idea in part, trivially, as “each microservice should own and control its own database and no two services should share a database.” The idea is sound: don't share a single database across services because then you run into conflicts like competing read/write patterns, data-model conflicts ...

Can we have single database in microservices?

You can use a single shared database with tables that owned by different microservices if your data is heavily related.

Why do microservices need to separate databases?

Creating a separate database for each service helps to enforce domain boundaries, but it's only one approach. There's nothing stopping you from having all your services share the same database. As long as your services behave and don't do unexpected things to data owned by other services, you'll be fine.

Expert · Answer