CacheU
Back to article

API Gateway

Work through each question. Reveal the answer when you're ready to check.

0 / 10 revealed
Q1Hardapi-gatewaymicroservicesdistributed-systems

Why do microservices architectures commonly require an API Gateway layer?

Q2Hardauthenticationapi-gatewaysecurity

Why is authentication commonly centralized at the API Gateway layer?

Q3Hardrate-limitingapi-gatewaybackend-protection

Why is rate limiting often implemented at the API Gateway instead of individual services?

Q4Hardapi-aggregationmicroserviceslatency-optimization

Why do API Gateways commonly perform request aggregation?

Q5Hardservice-discoveryapi-gatewaydistributed-systems

Why does an API Gateway require integration with service discovery systems?

Q6Hardapi-gatewaysingle-point-of-failuredistributed-systems

Why can an API Gateway become a dangerous bottleneck in distributed architectures?

Q7Hardobservabilitytracingapi-gateway

Why are API Gateways important for observability in microservices systems?

Q8Hardssl-terminationapi-gatewaycryptography

Why is SSL/TLS termination commonly handled at the API Gateway layer?

Q9Hardapi-versioningbackward-compatibilityapi-gateway

Why is API versioning often managed through API Gateways?

Q10Hardapi-gatewaytrade-offssystem-design

What are the major trade-offs when introducing an API Gateway in distributed systems?