Blog

Your dream job? Lets Git IT.
Interactive technical interview preparation platform designed for modern developers.

XGitHub

Platform

  • Categories

Resources

  • Blog
  • About the app
  • FAQ
  • Feedback

Legal

  • Privacy Policy
  • Terms of Service

© 2025 LetsGit.IT. All rights reserved.

LetsGit.IT/Categories/Microservices
Microserviceseasy

Why is sharing one database between microservices risky?

Tags
#shared-database#coupling#data-ownership
Back to categoryPractice quiz

Answer

It couples services through shared schema and transactions: one change can break others, deployments must be coordinated, and ownership becomes unclear. It also makes scaling and security boundaries harder.

Related questions

Monoliths
What is a “big ball of mud” and how can you recognize it?
#maintainability#coupling#code-smell
Monoliths
What is a “distributed monolith” and how do you avoid it?
#distributed-monolith#coupling#microservices
Monoliths
Database split during extraction — what is the hardest part?
#database#migration#data-ownership
Architecture
Coupling vs cohesion — what do you want and why?
#coupling#cohesion#design