Shared database anti-pattern in Microservices - Scalability & System Analysis

Scalability Analysis - Shared database anti-pattern

Growth Table: Shared Database Anti-Pattern

Users	What Changes
100 users	Single database handles all microservices; low contention; simple coordination.
10,000 users	Database load increases; contention on shared tables; slower transactions; microservices tightly coupled.
1,000,000 users	Database becomes bottleneck; high latency; schema changes affect multiple services; difficult to deploy independently.
100,000,000 users	Database overloads; scaling vertically is costly; outages impact all services; no isolation; very hard to maintain and evolve.

First Bottleneck

The shared database is the first bottleneck. As all microservices read and write to the same database, contention and locking increase. This causes slow queries and blocks other services. Schema changes become risky because they affect all services, reducing agility.

Scaling Solutions

• Database per service: Each microservice owns its own database to reduce contention and coupling.
• API communication: Services communicate via APIs instead of sharing data directly.
• Event-driven architecture: Use events to sync data asynchronously between services.
• Read replicas and caching: For read-heavy workloads, use replicas and caches to reduce load.
• Data partitioning: Split data by service domain to isolate workloads.

Back-of-Envelope Cost Analysis

Assuming 1 million users generate 10,000 requests per second total:

• Database QPS needed: ~10,000 QPS (likely exceeds single DB capacity).
• Storage: Shared DB grows fast, schema changes affect all services, increasing maintenance cost.
• Bandwidth: Internal network traffic increases due to contention and locking delays.
• Scaling vertically (bigger DB server) becomes expensive and hits limits quickly.

Interview Tip

Start by explaining the shared database anti-pattern and why it causes tight coupling and scaling issues. Then discuss how the database becomes a bottleneck as traffic grows. Finally, propose solutions like database per service and asynchronous communication to improve scalability and independence.

Self Check

Your database handles 1000 QPS. Traffic grows 10x to 10,000 QPS. What do you do first?

Answer: The first step is to decouple microservices by giving each its own database to reduce contention. Then introduce caching and read replicas to handle read load. This prevents the shared database from becoming a bottleneck.

Key Result

A shared database causes tight coupling and contention among microservices, becoming the first bottleneck as traffic grows. Decoupling databases per service and asynchronous communication are key to scaling.

Practice

1. What is the main problem caused by the shared database anti-pattern in microservices?

easy

A. Better fault isolation between services

B. Tight coupling between services due to shared data schema

C. Easier scaling of individual services

D. Improved performance by sharing data directly

Solution

1. Step 1: Understand the shared database anti-pattern

   This anti-pattern happens when multiple microservices use the same database schema directly.

2. Step 2: Identify the impact on service independence

   Sharing the database causes tight coupling, making services dependent on each other's data structure changes.

3. Final Answer:

   Tight coupling between services due to shared data schema -> Option B

4. Quick Check:

   Shared database = Tight coupling [OK]

Hint: Shared DB means tight coupling, breaking microservices independence [OK]

Common Mistakes:

• Thinking shared DB improves scaling
• Assuming shared DB isolates faults
• Believing shared DB simplifies service design

2. Which of the following is the correct way to avoid the shared database anti-pattern in microservices?

easy

A. Use a single database schema shared by all services

B. Store all data in a centralized monolithic database

C. Allow direct SQL queries from one service to another's database

D. Each service owns its own database and communicates via APIs

Solution

1. Step 1: Recall best practice for microservice data management

   Each microservice should have its own database to maintain independence.

2. Step 2: Identify the correct communication method

   Services communicate through APIs, not by sharing databases or direct queries.

3. Final Answer:

   Each service owns its own database and communicates via APIs -> Option D

4. Quick Check:

   Separate DB + APIs = Avoid shared DB anti-pattern [OK]

Hint: Separate DB per service + API calls avoid shared DB anti-pattern [OK]

Common Mistakes:

• Choosing shared schema for simplicity
• Allowing direct cross-service DB queries
• Centralizing all data in one DB

3. Consider two microservices, Service A and Service B, sharing the same database. Service A changes a table schema without informing Service B. What is the most likely outcome?

medium

A. Service B automatically adapts to the new schema

B. Service B continues working without issues

C. Service B experiences runtime errors due to schema mismatch

D. Both services improve performance

Solution

1. Step 1: Analyze the impact of schema change on shared DB

   When services share a database, schema changes affect all services using it.

2. Step 2: Predict Service B's behavior

   Service B expects the old schema; a change causes runtime errors like failed queries or crashes.

3. Final Answer:

   Service B experiences runtime errors due to schema mismatch -> Option C

4. Quick Check:

   Schema change + shared DB = runtime errors [OK]

Hint: Schema change in shared DB breaks other services [OK]

Common Mistakes:

• Assuming automatic schema adaptation
• Believing no impact on other services
• Thinking performance improves

4. You find that two microservices share a database causing tight coupling and deployment issues. Which change fixes this problem?

medium

A. Create separate databases and add API communication

B. Merge the two services into one monolith

C. Add more indexes to the shared database

D. Allow both services to write to the same tables

Solution

1. Step 1: Identify the root cause of tight coupling

   Sharing the same database schema causes deployment and coupling problems.

2. Step 2: Apply the correct fix

   Separating databases and using APIs decouples services and allows independent deployment.

3. Final Answer:

   Create separate databases and add API communication -> Option A

4. Quick Check:

   Separate DB + APIs fix shared DB anti-pattern [OK]

Hint: Separate DB + APIs fix tight coupling from shared DB [OK]

Common Mistakes:

• Merging services loses microservice benefits
• Adding indexes doesn't fix coupling
• Allowing shared writes keeps tight coupling

5. A company has three microservices sharing one database. They want to migrate to avoid the shared database anti-pattern. Which approach best balances data consistency and service independence?

hard

A. Split databases per service and use event-driven messaging for data sync

B. Keep shared database but add strict schema versioning

C. Merge all services into a single database schema with shared tables

D. Use direct SQL queries between services to keep data consistent

Solution

1. Step 1: Understand the trade-offs in migration

   Separating databases improves independence but can cause data consistency challenges.

2. Step 2: Choose a pattern that balances consistency and independence

   Event-driven messaging allows services to sync data asynchronously while keeping separate databases.

3. Final Answer:

   Split databases per service and use event-driven messaging for data sync -> Option A

4. Quick Check:

   Separate DB + events balance consistency and independence [OK]

Hint: Use separate DB + events for sync to avoid shared DB anti-pattern [OK]

Common Mistakes:

• Keeping shared DB limits independence
• Merging services loses microservice benefits
• Using direct SQL breaks service boundaries