Shared database anti-pattern in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the shared database anti-pattern in microservices?

It is when multiple microservices directly access the same database schema or tables, causing tight coupling and reducing service independence.

beginner

Why is the shared database anti-pattern problematic?

Because it breaks the principle of service autonomy, making it hard to deploy, scale, or change services independently.

intermediate

What is a better alternative to the shared database anti-pattern?

Each microservice should have its own database or schema and communicate with others through APIs or messaging, preserving loose coupling.

intermediate

How does the shared database anti-pattern affect data consistency?

It can cause data integrity issues because multiple services might update the same data without coordination, leading to conflicts.

beginner

What real-life analogy helps explain the shared database anti-pattern?

It's like several roommates sharing one notebook to write their schedules, causing confusion and conflicts instead of each having their own planner.

What does the shared database anti-pattern violate in microservices?

A Data encryption

B Service autonomy

C Load balancing

D User authentication

The shared database anti-pattern violates service autonomy by tightly coupling services through a common database.

Which is a common consequence of using a shared database in microservices?

A Tight coupling between services

B Independent service deployment

C Improved fault isolation

D Simplified API design

Using a shared database causes tight coupling, making services dependent on each other's data structure.

What is a recommended practice instead of sharing a database in microservices?

A Each service owning its database

B Using a monolithic database

C Sharing a single schema

D Direct database calls between services

Each microservice should own its database to maintain independence and loose coupling.

How can microservices communicate without sharing a database?

A Common database triggers

B Direct SQL queries

C Shared file system

D APIs or messaging systems

Microservices communicate via APIs or messaging to exchange data without sharing databases.

What problem arises when multiple services update the same shared database tables?

A Faster query performance

B Simplified backups

C Data conflicts and integrity issues

D Improved scalability

Multiple services updating the same data can cause conflicts and break data integrity.

Explain the shared database anti-pattern and why it is discouraged in microservices.

Think about how sharing one notebook among friends can cause confusion.

Describe how microservices should handle data storage to avoid the shared database anti-pattern.

Imagine each friend having their own planner and sharing updates by talking.

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