Master the IT-English vocabulary of distributed transactions: the saga pattern, compensating actions, orchestration vs choreography and eventual consistency.
0 / 10 completed
1 / 10
Why is a single ACID transaction hard across microservices?
With a database-per-service, you can't span one ACID transaction across services, so patterns like saga are used.
2 / 10
In the 'saga pattern', a multi-step operation is modelled as what?
A saga is a series of local transactions across services, coordinated to achieve an overall outcome.
3 / 10
If a saga step fails, a 'compensating action' is run. What does it do?
Compensating actions roll back earlier steps' effects (e.g. refund a charge) since there's no global rollback.
4 / 10
What distinguishes 'orchestration' from 'choreography' in sagas?
Orchestration centralises control in a coordinator; choreography is decentralised via event reactions.
5 / 10
Which sentence correctly uses 'eventual consistency' for sagas?
Sagas trade immediate consistency for eventual consistency, with the system converging once steps finish.
6 / 10
During a code review for the 'Order Processing' service, Sarah mentions that we're using a Saga pattern to handle order creation. Mark asks: 'So, if one of the steps – updating the inventory – fails, what's the primary goal of running a compensating action in this scenario?'
The core purpose of a compensating action in a Saga is to undo or rollback the effects of a previous operation if it fails. It's about maintaining data integrity within the distributed transaction. Options A and B accurately describe this – a compensating action *reverts* changes made by the failed step, which is key to the Saga's resilience. Options C and D misrepresent the role; orchestration doesn't directly handle compensation, and permanent cancellation isn't part of the Saga logic.
7 / 10
In a Slack channel discussing the implementation of a distributed order fulfillment system, David writes: 'We're using choreography for our saga. Each service publishes events to trigger the next step – it's like a decentralized dance.' Which of the following best describes this approach?
Choreography in Sagas emphasizes decentralization. Each service listens for events and then performs its designated action based on those events – akin to an independent 'dance'. This contrasts with orchestration, where a central entity dictates the flow. Option A is incorrect because choreography doesn't involve a single point of control; all services are autonomous. Options B and C also misrepresent how choreography works.
8 / 10
You're drafting a pull request description for a new feature that uses the Saga pattern to handle payments. You want to explain the concept clearly. Which of the following statements accurately describes eventual consistency within this context?
Eventual consistency is crucial for distributed systems like Sagas. It acknowledges that updates propagate asynchronously across services. There's a temporary period of divergence (different views), but the system will eventually reach a consistent state. Options A and B are incorrect – immediate consistency isn't guaranteed in a distributed environment, and synchronous updates aren't feasible. Option C misrepresents the timeline; it's not about blocking users.
9 / 10
During a standup meeting, you are discussing the 'Shipping Service' component of your e-commerce Saga. The team lead asks: 'What is the primary difference between using orchestration and choreography for this service?'
The core distinction lies in centralized control. Orchestration utilizes a central orchestrator that dictates the order of events and manages dependencies – whereas choreography allows services to react independently based on received events. This difference impacts complexity, robustness, and operational overhead. Option A accurately captures this fundamental contrast.
10 / 10
You're reviewing the documentation for a new microservice that handles user account creation within an e-commerce Saga. The document states: 'Upon successful account creation, the service emits an 'AccountCreated' event.' What does this indicate about how subsequent services will respond?
The emission of an 'AccountCreated' event signifies a publish-subscribe pattern. Other services—those interested in this specific event—will subscribe to it and react accordingly. This is a fundamental element of choreography in Sagas, where services communicate through events rather than direct calls. Option A misrepresents the communication model.
What will I practise in "Saga & Distributed Transaction Patterns"?
This module focuses on Microservices Language — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Microservices Language exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around microservices language — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Microservices Language exercises?
See the Microservices Language hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.