Database Per Service:

Sharing a single database across all microservices creates a "tight coupling" that prevents teams from deploying independently. This "shared state" means a schema change in one service can break five others. The Database Per Service pattern gives every microservice its own private store. This allows teams to choose the best database for their specific needs and deploy whenever they want without fear.