# 04 - Database Design for Modular Monolith: Schema Sharing vs Separation

Design databases for modular monolith: shared schema vs per-context schema trade-offs, managing pseudo-distributed transactions, data access patterns, and when to migrate to per-service databases.

## What you'll learn

- Shared Schema Advantages
- Shared Schema Disadvantages
- Intra-Module ACID Transactions
- Cross-Module Eventual Consistency
- 1. API Composition

*This article is part of the **Architecture** series on federicocalo.dev.*

---

## Read the full article

The complete article (13 min read) with code examples, diagrams, and practical exercises is available here:

**➡️ [04 - Database Design for Modular Monolith: Schema Sharing vs Separation](https://federicocalo.dev/en/blog/database-design-modular-monolith-schema-pattern)**

`https://federicocalo.dev/en/blog/database-design-modular-monolith-schema-pattern`

---

*By [Federico Calò](https://federicocalo.dev) — Software Developer & Technical Writer*