Data consistency challenges in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Eventual Consistency in Microservices

In a microservices system using asynchronous messaging, what is the main characteristic of eventual consistency?

A Data is never synchronized between services.

B All services have the same data instantly after an update.

C Services may temporarily have different data but will converge eventually.

D Services update data only when manually triggered.

💡 Hint

Think about how data synchronization happens over time in distributed systems.

Eventual consistency means that after some time, all services will have the same data, but not immediately after an update.

❓ Architecture

intermediate

Choosing a Data Consistency Model for Inventory Service

You design an inventory microservice that must reflect stock changes immediately to avoid overselling. Which consistency model suits best?

A Eventual consistency with asynchronous updates.

B Manual reconciliation after batch updates.

C No consistency, allow stale reads.

D Strong consistency with synchronous database transactions.

💡 Hint

Consider the risk of selling items that are not in stock.

Strong consistency ensures immediate data accuracy, preventing overselling by synchronously updating stock.

❓ scaling

advanced

Scaling a Microservices System with Consistency Constraints

When scaling a microservices system that requires strong consistency, what is a common tradeoff?

A Unlimited throughput without delays.

B Higher latency due to synchronous coordination.

C No need for distributed locks or consensus.

D Instant data replication without network overhead.

💡 Hint

Think about what synchronous coordination requires across services.

Strong consistency often requires coordination like distributed locks, which increases latency and limits throughput.

❓ tradeoff

advanced

Tradeoffs Between Eventual and Strong Consistency

Which statement correctly describes a tradeoff between eventual and strong consistency in microservices?

A Eventual consistency provides lower latency but may show stale data temporarily.

B Strong consistency always improves system availability.

C Eventual consistency requires synchronous database transactions.

D Strong consistency eliminates all network delays.

💡 Hint

Consider latency and data freshness differences.

Eventual consistency reduces latency by allowing temporary stale data, while strong consistency ensures fresh data but with higher latency.

❓ estimation

expert

Estimating Impact of Consistency Model on System Throughput

A microservices system processes 10,000 requests per second. Using strong consistency with synchronous commits adds 10ms latency per request. Estimate the maximum throughput impact compared to eventual consistency with near-zero latency.

A Throughput reduces to about 100 requests per second due to latency.

B Throughput remains at 10,000 requests per second with no impact.

C Throughput reduces to about 1,000 requests per second due to latency.

D Throughput doubles because of synchronous commits.

💡 Hint

Calculate how latency affects requests per second capacity.

10ms latency per request means each request takes longer, reducing max throughput roughly to 100 requests per second (1000ms / 10ms).