5 exercises — practice the language for integration patterns, ESB, API gateways, event brokers, and hub-and-spoke vs point-to-point discussions.
0 / 5 completed
1 / 5
Your architecture team is debating between two integration topologies.
A colleague says: "Point-to-point integrations worked when we had five systems. Now we have forty — we need a hub-and-spoke model."
What problem is the colleague describing?
The core problem with point-to-point integration is combinatorial explosion. With 5 systems: 10 connections. With 40 systems: 780 connections. Each is a custom pipeline to maintain, monitor, and modify when either system changes. A hub-and-spoke model (ESB, API gateway, or event broker as the hub) reduces this to n connections — each system connects once to the hub. The tradeoff: the hub becomes a single point of failure and a potential bottleneck.
2 / 5
An architect recommends using an API gateway as the integration layer.
Which statement best describes the role of an API gateway?
An API gateway sits at the north-south traffic boundary (external consumers → internal services) and centralises cross-cutting concerns: authentication/authorisation, rate limiting, SSL termination, request routing, protocol translation (REST↔gRPC), and logging. Examples: AWS API Gateway, Kong, Apigee, Azure API Management. Distinguish from a service mesh (east-west, internal service-to-service) and an ESB (broader orchestration, transformation, routing).
3 / 5
Complete the architecture decision from an integration review:
"For our order processing pipeline, we chose an _____ broker over synchronous REST calls — this decouples the order service from fulfilment and allows each to scale independently without blocking."
An event broker (Kafka, RabbitMQ, AWS SNS/SQS, Azure Service Bus) enables asynchronous, decoupled communication. Publishers emit events; subscribers consume them independently. The language "decouples... allows each to scale independently without blocking" is the canonical justification for choosing an event broker over synchronous REST. Note: "message broker" is also widely used and broadly acceptable — the distinction is that event brokers (like Kafka) retain event history, while traditional message brokers (like RabbitMQ) delete messages after delivery.
4 / 5
During a migration discussion, the team references an ESB (Enterprise Service Bus).
What is an ESB, and what is a common criticism of the pattern?
An ESB was the dominant enterprise integration pattern of the 2000s. It centralises routing, transformation, orchestration, and protocol translation. The classic criticism (popularised by microservices advocates) is that ESBs become "smart pipes" that accumulate business logic — violating the principle that services should be the source of truth for their own behaviour. Martin Fowler's "dumb pipes, smart endpoints" is the counter-pattern. That said, ESBs remain appropriate in many enterprise contexts where centralised governance and transformation are required.
5 / 5
Which sentence correctly uses integration architecture vocabulary in a design review?
Option B uses vocabulary correctly and quantifiably: point-to-point mesh (the problem), event broker (the solution), reduction in connections (the measured benefit), and event replay (an additional capability). This is the language of a credible integration architecture decision. Option A is a contradiction — ESB and point-to-point are alternative patterns. Option D confuses ESB (integration middleware) with service mesh (infrastructure layer for east-west traffic).
What does the "Integration Architecture Vocabulary — Enterprise Architecture English Exercise" exercise cover?
Practice English for integration architecture: ESB, API gateway, event broker, hub-and-spoke vs point-to-point, and integration pattern discussion language. 5 exercises.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Integration Architecture Vocabulary — Enterprise Architecture English Exercise"?
This exercise has 5 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Enterprise Architecture Language exercises?
Browse the full Enterprise Architecture Language hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.