Bird
Raised Fist0
Microservicessystem_design~10 mins

Database decomposition strategy in Microservices - Interactive Code Practice

Choose your learning style10 modes available

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to define a microservice with its own database.

Microservices
class [1]Service:
    def __init__(self):
        self.database = DatabaseConnection('user_db')
Drag options to blanks, or click blank then click option'
AUser
BOrder
CInventory
DPayment
Attempts:
3 left
💡 Hint
Common Mistakes
Choosing a service that does not manage user data.
2fill in blank
medium

Complete the code to route a request to the correct microservice based on the database decomposition.

Microservices
def route_request(request):
    if request.type == 'order':
        return [1]Service.handle(request)
Drag options to blanks, or click blank then click option'
AUser
BPayment
COrder
DInventory
Attempts:
3 left
💡 Hint
Common Mistakes
Routing order requests to UserService or unrelated services.
3fill in blank
hard

Fix the error in the database access code for the Inventory microservice.

Microservices
class InventoryService:
    def get_stock(self, item_id):
        return self.db.[1]('SELECT stock FROM inventory WHERE id = %s', item_id)
Drag options to blanks, or click blank then click option'
Acommit
Bexecute
Cfetchall
Dconnect
Attempts:
3 left
💡 Hint
Common Mistakes
Using fetchall before execute, or commit/connect incorrectly.
4fill in blank
hard

Fill both blanks to correctly implement database decomposition with separate connections and queries.

Microservices
class [1]Service:
    def __init__(self):
        self.db = DatabaseConnection('[2]_db')
Drag options to blanks, or click blank then click option'
APayment
Buser
Corder
DInventory
Attempts:
3 left
💡 Hint
Common Mistakes
Mixing service names and database names incorrectly.
5fill in blank
hard

Fill all three blanks to implement a query filtering orders by status in the Order microservice.

Microservices
def get_orders_by_status(self, status):
    query = "SELECT * FROM orders WHERE status [1] %s"
    self.db.[2](query, (status,))
    return self.db.[3]()
Drag options to blanks, or click blank then click option'
A=
Bexecute
Cfetchall
Dcommit
Attempts:
3 left
💡 Hint
Common Mistakes
Using commit instead of execute or fetchall, or wrong SQL operator.

Practice

(1/5)
1. Which of the following best describes vertical decomposition in database design for microservices?
easy
A. Dividing a database by rows to distribute data across multiple databases
B. Combining multiple databases into one large database
C. Separating databases based on geographic location
D. Splitting a database by grouping related tables or columns into separate databases

Solution

  1. Step 1: Understand vertical decomposition

    Vertical decomposition means splitting a database by grouping related tables or columns, often by business capability or domain.
  2. Step 2: Compare with other options

    Horizontal decomposition splits by rows, geographic is location-based, and combining is the opposite of decomposition.
  3. Final Answer:

    Splitting a database by grouping related tables or columns into separate databases -> Option D
  4. Quick Check:

    Vertical decomposition = splitting by columns/tables [OK]
Hint: Vertical = split by columns or tables, horizontal = split by rows [OK]
Common Mistakes:
  • Confusing vertical with horizontal decomposition
  • Thinking vertical means geographic split
  • Assuming decomposition means combining databases
2. Which of the following is the correct description of horizontal decomposition in microservices database design?
easy
A. Dividing data by rows, such as by customer or region
B. Splitting data by columns or tables based on functionality
C. Merging multiple databases into one for simplicity
D. Separating databases by different database engines

Solution

  1. Step 1: Define horizontal decomposition

    Horizontal decomposition splits data by rows, for example, dividing customers by region or user ID ranges.
  2. Step 2: Eliminate incorrect options

    Splitting data by columns or tables based on functionality describes vertical decomposition, C is merging (not decomposition), and D is about engines, not decomposition strategy.
  3. Final Answer:

    Dividing data by rows, such as by customer or region -> Option A
  4. Quick Check:

    Horizontal decomposition = split by rows [OK]
Hint: Horizontal = split by rows, vertical = split by columns [OK]
Common Mistakes:
  • Mixing horizontal with vertical decomposition
  • Thinking horizontal means merging databases
  • Confusing database engine separation with decomposition
3. Consider a microservices system where the user database is split by region using horizontal decomposition. If a query requests all users from Europe, which database(s) will be queried?
medium
A. Only the database shard containing European users
B. All database shards regardless of region
C. Only the database shard containing North American users
D. A combined database with all users merged

Solution

  1. Step 1: Understand horizontal decomposition by region

    Horizontal decomposition splits data by rows, so each shard holds users from a specific region.
  2. Step 2: Identify which shard to query

    Querying European users targets only the shard holding European data, not others.
  3. Final Answer:

    Only the database shard containing European users -> Option A
  4. Quick Check:

    Query targets relevant shard only [OK]
Hint: Query only the shard holding requested data region [OK]
Common Mistakes:
  • Querying all shards unnecessarily
  • Querying wrong region shard
  • Assuming data is merged in one database
4. A microservices team decomposed their database vertically but notices frequent cross-service joins causing latency. What is the likely cause and fix?
medium
A. Cause: Using NoSQL instead of SQL; Fix: Switch to SQL databases
B. Cause: Horizontal decomposition; Fix: Merge databases into one
C. Cause: Poor vertical decomposition causing cross-service joins; Fix: Redesign to reduce cross-service dependencies
D. Cause: Too many database shards; Fix: Increase shards further

Solution

  1. Step 1: Identify problem with vertical decomposition

    Vertical decomposition splits by tables/domains, but if services need to join data often, it causes latency.
  2. Step 2: Recommend fix

    Redesign to reduce cross-service joins by better domain boundaries or data duplication to avoid latency.
  3. Final Answer:

    Poor vertical decomposition causing cross-service joins; Fix: Redesign to reduce cross-service dependencies -> Option C
  4. Quick Check:

    Cross-service joins cause latency; fix by better decomposition [OK]
Hint: Cross-service joins mean bad vertical split; redesign domains [OK]
Common Mistakes:
  • Confusing horizontal with vertical decomposition issues
  • Thinking merging databases fixes latency
  • Blaming database type instead of design
5. A company wants to scale their microservices database by splitting user data by country (horizontal) and splitting user profile and orders into separate databases (vertical). What is the best approach to handle queries that need both profile and order data for users in a specific country?
hard
A. Perform cross-database joins directly on all shards for each country
B. Use API composition to aggregate data from profile and order services after querying country-specific shards
C. Merge profile and order data into a single database shard per country
D. Store all user data in one large database to avoid complexity

Solution

  1. Step 1: Understand combined vertical and horizontal decomposition

    Data is split horizontally by country and vertically by data type (profile, orders), so data is in different shards and databases.
  2. Step 2: Choose best query approach

    Cross-database joins are expensive and complex; merging data loses benefits. API composition aggregates data from services after querying relevant shards efficiently.
  3. Final Answer:

    Use API composition to aggregate data from profile and order services after querying country-specific shards -> Option B
  4. Quick Check:

    API composition handles multi-db queries efficiently [OK]
Hint: Use API composition to combine data from vertical and horizontal splits [OK]
Common Mistakes:
  • Trying cross-database joins causing latency
  • Merging databases losing scalability
  • Ignoring decomposition benefits for simplicity