Microservices Data Management Strategies 2

Question 1

In a microservices architecture, what does the 'Database per Service' pattern primarily ensure?

Accepted Answer

Each service owns and encapsulates its own data store

Answer

Database per Service gives each microservice exclusive ownership of its data, preventing tight coupling at the data layer.

Question 2

Which pattern is commonly used to maintain data consistency across services without distributed transactions?

Accepted Answer

Saga pattern

Answer

The Saga pattern coordinates a sequence of local transactions with compensating actions instead of a distributed transaction.

Question 3

What is a key drawback of sharing a single database across multiple microservices?

Accepted Answer

It creates tight coupling and hinders independent deployment

Answer

A shared database couples services through the schema, making independent evolution and deployment difficult.

Question 4

In the Saga pattern, what is a 'compensating transaction'?

Accepted Answer

An operation that undoes the effect of a previously completed transaction

Answer

Compensating transactions reverse prior steps when a later step in the saga fails, restoring consistency.

Question 5

Which approach allows services to maintain a local read-optimized copy of data owned by another service?

Accepted Answer

Data replication via event-driven updates

Answer

Services can replicate needed data locally and keep it updated through events, avoiding cross-service queries.

Microservices Practice Test