Shared database anti-pattern in Microservices - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to identify the main issue with shared databases in microservices.

Microservices

The shared database anti-pattern causes [1] between microservices.

Drag options to blanks, or click blank then click option'

Adata isolation

Bloose coupling

Cindependent scaling

Dtight coupling

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing loose coupling, which is the opposite of the problem.

Confusing data isolation with shared data.

Shared databases cause tight coupling because services depend on the same data structure.

2fill in blank

medium

Complete the code to explain a consequence of the shared database anti-pattern.

Microservices

One consequence is that [1] can become a bottleneck for all services.

Drag options to blanks, or click blank then click option'

Athe shared database

Bthe network

Cthe user interface

Dthe cache

Attempts:

3 left

💡 Hint

Common Mistakes

Selecting network or cache, which are not the main bottlenecks here.

The shared database can slow down all services because they all access it.

3fill in blank

hard

Fix the error in the statement about shared database anti-pattern.

Microservices

Shared databases do not allow microservices to [1] their data independently.

Drag options to blanks, or click blank then click option'

Aisolate

Bshare

Cupdate

Dmanage

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing 'update' or 'manage' which imply control but miss the isolation issue.

Shared databases prevent services from isolating their data, causing tight coupling.

4fill in blank

hard

Fill both blanks to describe a better alternative to shared databases.

Microservices

Use [1] databases and [2] communication between services.

Drag options to blanks, or click blank then click option'

Aseparate

Bshared

Casynchronous

Dsynchronous

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing shared databases or synchronous communication, which keep tight coupling.

Separate databases reduce coupling, and asynchronous communication improves scalability.

5fill in blank

hard

Fill all three blanks to complete the microservices design avoiding shared database anti-pattern.

Microservices

Each service owns its [1], communicates via [2], and uses [3] for data consistency.

Drag options to blanks, or click blank then click option'

Adatabase

Bevents

Ceventual consistency

Dshared cache

Attempts:

3 left

💡 Hint

Common Mistakes

Selecting shared cache, which reintroduces coupling.

Owning databases, using events for communication, and eventual consistency help avoid tight coupling.