Learn vocabulary for synchronous vs. asynchronous communication, request-reply, publish-subscribe, idempotency, and exactly-once delivery in microservices.
0 / 10 completed
1 / 10
What distinguishes synchronous from asynchronous communication in microservices vocabulary?
Synchronous (REST, gRPC): caller blocks waiting for a response — simple to reason about but creates temporal coupling (both services must be available simultaneously). Asynchronous (Kafka, RabbitMQ, SQS): caller publishes a message to a broker and continues — receiver processes it when ready. Async decouples availability but adds complexity (message ordering, at-least-once delivery, consumer lag).
2 / 10
What is the 'request-reply' pattern in microservices communication vocabulary?
Request-reply over messaging: the caller publishes a request with a correlation ID and a reply-to address (queue/topic). The receiver processes the request and publishes the response to the reply-to address with the same correlation ID. The caller consumes from its reply queue and matches responses by correlation ID. This gives request-reply semantics with async decoupling.
3 / 10
What is the 'publish-subscribe' (pub-sub) pattern in microservices vocabulary?
Pub-sub (Kafka topics, SNS, Google Pub/Sub): producers publish events to a topic; multiple independent consumers subscribe. Each subscriber sees all messages (or a filtered subset). The producer has no knowledge of subscribers. This enables fan-out: OrderPlaced event can trigger inventory reservation, email notification, and analytics ingestion all independently, with no coupling between those consumers.
4 / 10
What is 'idempotency' in microservices communication vocabulary?
Idempotency is essential for reliable messaging: since 'at-least-once delivery' means messages can arrive more than once, consumers must handle duplicates safely. Techniques: idempotency keys (store processed message IDs in a deduplication table; skip if already seen), natural idempotency (PUT /orders/123 with full state is idempotent; POST /orders is not). Design APIs and consumers to be idempotent by default.
5 / 10
What does 'exactly-once delivery' mean in microservices messaging vocabulary?
Delivery semantics: at-most-once (may lose messages, never duplicates), at-least-once (never loses messages, may duplicate — most common), exactly-once (no loss, no duplicates — hardest to achieve). Kafka provides exactly-once semantics (EOS) via idempotent producers + transactional APIs, but at significant complexity cost. In practice, most systems use at-least-once + idempotent consumers.
6 / 10
During a stand-up meeting with the DevOps team, Sarah mentions needing to 'decouple' the user authentication service. What does 'decoupling' typically refer to in the context of microservices communication?
'Decoupling' in microservices means creating independent services with minimal reliance on each other. This allows teams to develop and deploy changes faster without affecting dependent services. Option A is incorrect as synchronous calls introduce tight coupling. Option C describes a different messaging pattern.
7 / 10
David, a senior developer, receives an API response from the payment service indicating a 'duplicate request.' Considering microservices communication vocabulary, what does this likely signify?
'Duplicate request' in microservices often indicates an idempotency issue. Idempotency means that performing the same operation multiple times has the same effect as doing it once. The payment service is likely preventing data corruption by rejecting subsequent attempts at processing the same transaction ID.
8 / 10
Maria is reviewing a pull request for a new microservice that uses a publish-subscribe pattern. She notices the service publishes events to a topic named 'UserCreated'. What is the *primary* benefit of this approach in terms of microservices communication?
The publish-subscribe pattern promotes loose coupling. Services subscribe to topics they are interested in without needing direct knowledge of publishers. This allows services to scale independently based on event consumption needs. Option A is incorrect as it doesn't address the core benefit of decoupling.
9 / 10
During a Slack conversation about designing a microservices architecture, John asks if they should implement 'exactly-once delivery' for all messages. What is the *most* important reason to prioritize this in the context of microservices?
'Exactly-once delivery' is crucial to prevent data corruption and ensure consistency in a distributed system. If a service processes an event multiple times due to failures or network issues, it can lead to incorrect results. Option A addresses capacity, while C focuses on latency.
10 / 10
In a PR description for a new microservice that interacts with another service via an API request, Alex describes the interaction as 'request-reply'. What does this pattern typically represent in microservices communication?
The 'request-reply' pattern is a fundamental synchronous communication model. The requesting service sends a request and blocks until the response is received. This provides immediate feedback about the success or failure of the operation, essential for building reliable interactions between microservices.
What will I practise in "Microservices Communication — 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.