Practice vocabulary for inter-service reliability: bulkhead pattern, timeout chains, cascading failures, retry storms, exponential backoff, and failure isolation.
0 / 10 completed
1 / 10
What does the 'bulkhead pattern' do in a microservices system?
The bulkhead pattern (named after ship compartments) isolates failures — if one service exhausts its thread pool or connection pool, it doesn't cascade to others.
2 / 10
A developer says: 'The ___ storm overwhelmed the downstream service.' What word is missing?
A 'retry storm' occurs when many upstream services simultaneously retry failed requests, amplifying load on an already-struggling downstream service.
3 / 10
'We implemented exponential ___.' Which word completes this?
'Exponential backoff' means doubling (or multiplying) the wait time between retry attempts, reducing load during incidents and preventing retry storms.
4 / 10
What is a 'cascading failure' in distributed systems?
A cascading failure happens when one service's failure propagates through dependency chains, causing multiple services to go down in sequence.
5 / 10
'We need to ___ the failure so it doesn't spread to other services.' Which verb fits?
'Isolate' is the standard verb for failure isolation — containing a fault within its origin service to prevent it from affecting the broader system.
6 / 10
Sarah (Lead Developer) commented on a PR: 'This retry logic feels like a bit of a brute force solution. We're essentially masking the underlying problem – the external API is consistently failing. I think we should investigate circuit breakers.' What does 'brute force' refer to in this context?
'Brute force' in this scenario describes an overly simple or forceful approach – in this case, repeatedly trying to access a failing API without addressing the root cause. The correct answer highlights that Sarah is concerned about masking the underlying problem by simply retrying, which isn't a reliable solution for intermittent failures. The other options represent more sophisticated approaches to handling unreliable external services.
7 / 10
Mark (DevOps Engineer) sent a Slack message: 'The service degradation after the database outage is exhibiting *blast radius* characteristics. We're seeing cascading failures impacting order processing and payment gateways.' What does 'blast radius' signify in this situation?
'Blast radius' is a common term in distributed systems referring to the degree to which an issue can propagate and affect other services or components. It's not about the initial severity of the outage (option C) or recovery time (option D), but rather how far the failure has spread. Mark is indicating that the problem isn't contained; it's actively causing problems in downstream systems.
8 / 10
David (Senior Developer) wrote a PR description: 'We implemented exponential *backoff* to handle temporary API unavailability.' What does 'exponential backoff' entail?
'Exponential backoff' is a technique for handling temporary failures of dependent services. It involves increasing the delay between retries exponentially – starting with a short delay and doubling it with each failed attempt. This prevents overwhelming the failing service and gives it time to recover, avoiding a cascading failure. Option C represents a linear backoff strategy.
9 / 10
John (DevOps) sent a Slack message: 'The service is experiencing intermittent latency spikes. We've observed an increasing number of requests timing out against the third-party authentication service. It appears we need to implement circuit breaker logic to prevent cascading failures.' What does 'circuit breaker' refer to in this context?
A 'circuit breaker' is not about physical hardware or simply monitoring metrics. It's a design pattern – an automated mechanism that actively *cuts off* communication with a failing service when it exceeds predefined thresholds, preventing further requests from being sent and thus mitigating cascading failures. Option A is incorrect; options C & D are related but don't represent the core function.
10 / 10
Maria (Senior Developer) left a comment on a code review: 'The current retry policy is too aggressive. It's repeatedly hammering the API without considering potential rate limits, leading to further service degradation.' What problem does Maria highlight regarding the retry policy?
Maria is pointing out a critical issue: the retry policy isn't adapting to the API's behavior. 'Rate limiting' occurs when an API restricts the number of requests from a single source within a given timeframe. A naive retry strategy will exacerbate this, leading to further failures and service degradation. Options A, B & C represent other potential problems but aren't the primary focus here.
What will I practise in "Inter-Service Reliability Vocabulary"?
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.