api-gateway-design

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

1|Updated Jun 20, 2026

Search Tags:#microservices #kubernetes #gitops #api-gateway #kong #edge-security

Ready to run

npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill api-gateway-design-shafibabar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: api-gateway-design
Source: https://github.com/shafibabar/SDLC-Artifact-Factory/tree/main/skills/api-gateway-design
Command: npx skills add https://github.com/shafibabar/SDLC-Artifact-Factory --skill api-gateway-design-shafibabar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill resolves the confusion between edge policy and service-mesh responsibilities, preventing the common anti-pattern of smearing cross-cutting concerns across microservices.

Core Features & Use Cases

Edge Policy Enforcement: Centralizes authentication, rate limiting, and TLS termination at the north-south boundary.
Declarative GitOps Management: Enables version-controlled gateway configuration using Kong Ingress Controller CRDs or decK.
Use Case: A platform engineer needs to deploy a managed entry point for a new microservices system that requires JWT validation and per-tenant rate limiting without modifying individual service code.

Quick Start

Use the api-gateway-design skill to generate a declarative Kong configuration manifest that implements TLS termination and JWT authentication for the new service ingress.

Frequently Asked Questions about api-gateway-design

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

FAQPage Schema

How do I centralize authentication and rate limiting for microservices without modifying service code?▼

To centralize authentication and rate limiting without modifying service code, enforce edge policies at the north-south API gateway boundary. This offloads cross-cutting concerns like JWT validation and per-tenant traffic control from individual microservices.

What is the difference between an API gateway and a service mesh for microservices?▼

An API gateway handles north-south traffic and edge policy enforcement, while a service mesh manages east-west communication between internal microservices. Separating these concerns prevents the anti-pattern of smearing cross-cutting policies across your services.

How do I configure a Kong API gateway using GitOps?▼

To configure a Kong API gateway using GitOps, use declarative configuration tools like Kong Ingress Controller CRDs or decK. This enables version-controlled management of gateway routing and policies for your microservices infrastructure.

Can I run a DB-less API gateway in a Kubernetes cluster?▼

Yes, you can run a DB-less API gateway in a Kubernetes cluster. This architecture supports declarative GitOps-managed infrastructure by storing configuration directly in memory or as declarative manifests, eliminating the need for a gateway database.

How do I handle TLS termination and JWT validation at the cluster boundary?▼

To handle TLS termination and JWT validation at the cluster boundary, deploy a north-south API gateway. It centralizes edge security by processing incoming traffic before routing it to the internal microservices.

When should I not use an API gateway for microservices traffic routing?▼

You should not use an API gateway for internal east-west microservices traffic routing. API gateways are designed for north-south edge policy enforcement, and using them for internal mesh concerns creates unnecessary latency and configuration complexity.