RTE logo
← Back to architecture map
Architecture Pattern

Shared Database

Multiple services share one DB. Simple but creates tight coupling and brittle schema changes.

⚠️ coupling

Flow From Map

Svc A ↘
Svc B → [Shared DB 💾]
Svc C ↗
⚠️ avoid in microservices!

Your POC Area

Replace this placeholder with your interactive proof of concept for Shared Database. This route is already dedicated to this pattern, so you can add diagrams, controls, code demos, or simulations here.

Example references: Monolith DB, legacy systems, Sequelize models

Comments

Sign in to leave a comment. Your name and photo come from Google; nothing else is shared.

Loading comments...