Broker Architecture Pattern – Match the Concepts
Drag-or-click each term on the left to its definition on the right, then press Check answers to see how you did.
Client Stub
Server Skeleton
Broker
Naming / Registry Service
Interface Definition Language (IDL)
Location Transparency
Load Balancing
Connection Pooling
Circuit Breaker
Service Discovery
Authentication & Authorization
TLS Termination / mTLS
Distributed Tracing
One-way Invocation
God Broker Anti-Pattern
Generated client-side proxy that marshals requests and hides transport details
Generated server-side proxy that unmarshals requests and invokes service logic
Intermediary that routes requests, enforces policies, and returns responses
Directory where services register and clients resolve endpoints at runtime
Language-neutral contract used to generate stubs and skeletons
Calling a service without knowing its physical network address
Distributing requests across multiple service instances for scale and resilience
Reusing network connections to cut handshake overhead and latency
Fail-fast guard that halts calls to an unhealthy service for a cooldown period
Automatic detection of available service instances and their health
Broker-enforced identity verification and access control for each call
Encryption (and optional mutual cert checks) handled transparently by the broker
Propagating trace IDs so a call can be followed across multiple services
Fire-and-forget call that sends a request without waiting for a response
Overloading the broker with business logic, turning it into a monolithic bottleneck