Grokking Microservices Design Patterns
Vote

0% completed

​

Performance Implications

As we saw in our Java example, the Saga Pattern solves the problem of data consistency in microservices. Like any other pattern, it has issues and special considerations. Here they are.

Issue 1: Complexity

The first issue is complexity. Remember how we split a large transaction into several smaller ones? That does ensure data consistency, but it also adds complexity. Each service in our saga now needs to handle its local transaction and provide a compensating transaction.

Consider our online shopping scenario

.....

.....

.....

Like the course? Get enrolled and start learning!
Mudassar Ali

Mudassar Ali

· 2 years ago

Is the orchestrator kind of two phase commits.

Also there is another pattern which i find more robust is outbox pattern its kind of choreography with addition guarantee that local transaction and event published are done in a transaction so that either both event and db is updated or both fail.

Show 1 reply

Reading Progress

0%

Vote for new content