Should different microservices share a database?

Question

You are not likely to benefit from a Microservices architecture if all the services share the same database tables. This is because you are effectively tightly coupling the services. If a database table changes all the services will have to change. 25 апр. 2017 г.

In the shared-database-per-service pattern, the same database is shared by several microservices. You need to carefully assess the application architecture before adopting this pattern, and make sure that you avoid hot tables (single tables that are shared among multiple microservices).

Should each microservice have separate 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).

Does each microservice have its own database?

The short answer is yes. However, before you start hyperventilating about the cost of all those extra Oracle licenses, lets first explore why it is essential to do this and then discuss what is meant by the term 'database'.

This article will take you through few approaches to build robust and self-contained Microservices without code duplication. First of all, it's essential not to duplicate code between Microservices, especially if it's the same code being copied and pasted. It can cause more harm than having dependencies.

Expert · Answer