Orchestration vs. Choreography: Two Ways to Implement the Saga Pattern
When building distributed systems, especially in fintech or e-commerce, a single transaction can span multiple services.
Imagine a checkout process:
- Reserve inventory
- Process payment
- Create shipment
❌ Harder to trace and debug as the number of events grows
Neither is universally better.
Small or straightforward workflows often benefit from orchestration.
Highly distributed systems with many independent services tend to benefit from choreography.
If you don't understand reconciliation, you have no business building fintech or banking applications. Moving money isn't just about debiting one account and crediting another.
Without a proper reconciliation process, you'll eventually end up asking one of the most expensive questions in fintech: "Where did the money go?"
Reconciliation isn't an optional feature, it's one of the foundations of every reliable financial system.
@Damilolawo1a The concept spans a wide range of topics from designing a well structured database that can withstand a high volume of requests without lagging, to scaling servers, integrating caching, load balancing etc. it goes beyond code. It's main purpose is to serve high volume of users.
You were asked in an interview: A database connection pool of 2,000 could only handle 10,000 requests, but a pool of 96 handled 20,000 requests. How would you answer?