Skip to content

STORY: Implement API Gateway rate limiting and downstream resilience #3

Closed
1 of 1 issue completed
Closed

Description

@ramioooz

Objective

Add edge-level protection and downstream resilience controls to API Gateway.

Scope

  • Add request rate limiting for public API routes.
  • Define per-route throttling settings through external configuration.
  • Add circuit breaker and retry policies for downstream service routes.
  • Return stable error responses when throttling or fallback behavior is triggered.
  • Keep the gateway free of business-domain logic.
  • Document local SIT verification through Insomnia and curl.

Acceptance Criteria

  • Customer Service routes are protected by a rate limiter.
  • Gateway route configuration remains externalized through Config Server and platform-config.
  • Downstream failures do not cascade indefinitely to clients.
  • Automated tests cover rate-limit and fallback behavior.
  • SIT deployment verifies the gateway still routes healthy downstream traffic.

Activity

  1. self-assigned this
    on Jun 25, 2026
  2. added theissue type on Jun 29, 2026
  3. ramioooz commented on Sep 3, 2026

    @ramioooz
    MemberAuthor

    Gateway resilience integration PR is ready for review: #22

    It integrates the reviewed API Gateway #20 and #21 stack into main, including Redis-backed rate limiting and the existing resilience controls. Verification passed: 16 tests, Helm validation, container smoke test, and git diff --check.

  4. ramioooz commented on Sep 4, 2026

    @ramioooz
    MemberAuthor

    Completed. All child outcomes are delivered: Redis-backed route-specific rate limiting in api-gateway#21, integrated gateway resilience and fail-closed behavior in api-gateway#22, and gateway authorization/security integration in api-gateway#23.

    The gateway resilience story is now complete for the current SIT scope. AWS/UAT/PROD promotion remains a later project boundary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions