OpenClaw LaunchOpenClaw Launch
🚪

API Gateway Patterns

Verified

by Community

Explores API gateway patterns including request routing, response aggregation, protocol translation, rate limiting, and authentication. Compares popular gateway solutions and helps you choose the right approach for your architecture.

api-gatewayroutingmicroservices

API Gateway Patterns

Design and implement API gateways that route traffic, aggregate responses, handle cross-cutting concerns, and provide a unified entry point for your microservices. Covers both build and buy decisions.

Usage

Ask about API gateway design decisions, routing strategies, or comparing gateway solutions for your use case.

Examples

  • "Should I build a custom API gateway or use an off-the-shelf solution?"
  • "How do I implement response aggregation in my gateway?"
  • "What cross-cutting concerns should my API gateway handle?"

Guidelines

  • Keep the gateway thin — avoid putting business logic in the gateway
  • Use the Backend for Frontend pattern for client-specific gateways
  • Implement rate limiting and authentication at the gateway level
  • Monitor gateway latency to ensure it doesn't become a bottleneck
  • Plan for gateway high availability since it is a single point of entry

More Architecture & Design Patterns Skills

🔀
CQRS Implementation

Separate read and write models for optimized query and command handling.

🧩
Domain-Driven Design

Model complex business domains with bounded contexts and aggregates.

⬡
Hexagonal Architecture

Build applications with ports and adapters for testability and flexibility.

🧹
Clean Architecture Guide

Organize code into concentric layers with dependency rules.