skills.rest
roanbrasil
roanbrasilCOMMUNITY
Explore all skills by this author →
Website𝕏@roanbrasilGitHub

api-gateway-design

Configure API gateways with authentication, rate limiting, and routing.

5|1|Updated Jun 17, 2026
Search Tags:#jwt#microservices#rate-limiting#bff#api-gateway#request-aggregation#circuit-breaking
One-click install
npx skills add https://github.com/roanbrasil/engineer-grade-agent-skills --skill api-gateway-design-roanbrasil
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-gateway-design
Source: https://github.com/roanbrasil/engineer-grade-agent-skills/tree/main/skills/api-gateway-design
Command: npx skills add https://github.com/roanbrasil/engineer-grade-agent-skills --skill api-gateway-design-roanbrasil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the security risks, operational inefficiencies, and poor client experience caused by unstandardized edge traffic handling for microservice architectures, where cross-cutting concerns like authentication, rate limiting, and routing are either duplicated across services or missing entirely.

Core Features & Use Cases

  • Multi-Platform Gateway Configuration: Implement production-ready routing, JWT authentication, token bucket rate limiting, SSL termination, and circuit breaking for leading gateway tools including Kong, AWS API Gateway, Traefik, and Spring Cloud Gateway.
  • BFF Pattern Implementation: Build client-specific Backend for Frontend layers to deliver optimized, minimal payloads for web, mobile, and IoT clients, eliminating over-fetching and under-fetching issues from generic shared APIs.
  • Resilience & Observability: Design request aggregation patterns, distributed tracing integration, and RED metrics monitoring for gateways and BFFs to ensure high availability and fast failure detection.
  • Real-World Use Case: For an e-commerce platform with web, iOS, and smart TV clients, use this skill to configure a central gateway for edge security and rate limiting, plus separate BFFs owned by each frontend team to serve client-optimized checkout and product data.

Quick Start

Use the api-gateway-design skill to configure a Kong API gateway with JWT validation, tiered rate limiting, and circuit breaking for your internal microservices, plus a mobile BFF that aggregates order, user, and product data into a lean checkout payload.

Frequently Asked Questions about api-gateway-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement the BFF pattern for web, mobile, and IoT clients?▼

The BFF pattern is implemented by building client-specific Backend for Frontend layers that aggregate order, user, and product data into lean payloads. This eliminates over-fetching and under-fetching issues caused by generic shared APIs.

How do I configure JWT authentication and rate limiting in Kong API Gateway?▼

Configure Kong API Gateway with JWT validation, token bucket rate limiting, SSL termination, and circuit breaking to centralize edge security. This eliminates duplicated authentication logic across your internal microservices.

What is the best way to handle cross-cutting concerns in a microservices architecture?▼

Centralize cross-cutting microservice traffic concerns including authentication, rate limiting, routing, and resilience at the API gateway layer. This eliminates duplication and security gaps across polyglot microservice environments.

Can I use AWS API Gateway and Traefik for circuit breaking and request aggregation?▼

Yes, you can configure production-grade gateway products including AWS API Gateway, Traefik, and Spring Cloud Gateway for circuit breaking and request aggregation. These tools support high availability and fast failure detection.

Do I need distributed tracing and RED metrics for my API gateway?▼

Yes, you need distributed tracing integration and RED metrics monitoring for gateways and BFFs to ensure high availability. This observability integration provides fast failure detection for production API infrastructure.

When should I not use a generic shared API for multiple frontend platforms?▼

Avoid generic shared APIs when serving web, iOS, and smart TV clients simultaneously. Instead, use separate BFFs owned by each frontend team to deliver optimized, minimal payloads for client-specific checkout and product data.

Related Skills

Explore More Software Engineering Skills→
allsmogallsmog
22

Mixed-Language Monorepos

Audit security of polyglot monorepos with language detection and cross-service threat modeling.

Community
Advanced
thiagoooo34252thiagoooo34252
1

engineer-observability

Configure structured logging, metrics, distributed tracing, and alerting for production systems.

Community
Advanced
franroafranroa

Microservices Architect

Decompose monoliths into microservices with domain-driven boundaries and service communication.

Community
Advanced
shafibabarshafibabar
1

api-gateway-design

Design north-south API gateway architecture for edge policy enforcement.

Community
Advanced