1. API Gateway advanced

    A developer platform's API gateway has accumulated business logic and become a bottleneck for every team. What should be moved out, and what belongs there?

    2 min answer api-gatewayscopebottleneckdistributed-monolith
  2. API Gateway advanced

    A public API is being overwhelmed by a handful of clients. Where should rate limiting live, which algorithm, and how should limits differ across users, tenants, endpoints and infrastructure?

    3 min answer rate-limitinggatewaycloudflaremulti-tenancy
  3. API Gateway advanced

    A ticketing platform at Ticketmaster's on-sale peaks routes everything through one gateway. Gateway to BFF to inventory is three hops and each hop retries up to three times on a timeout or a 5xx. Inventory's p99 crosses its 400 ms timeout at 09:00:02. Walk the next ninety seconds and say where the limit actually has to live.

    3 min answer api gatewayretriesretry budgetadmission control
  4. API Gateway intermediate

    An API gateway has accumulated authentication, rate limiting, routing, response transformation, request validation and some business logic. Which of these belong there?

    2 min answer razorpaygatewaycross-cuttingcoupling
  5. API Gateway beginner

    An API gateway validates every external token and strips the caller's credentials before forwarding, so the order service is configured to trust any request arriving on the internal network. Six weeks later a batch job owned by another team creates refunds against live accounts. Why did the gateway not prevent that, and what is the smallest change that does?

    3 min answer api-gatewayauthenticationauthorisationdefence-in-depth