api-gateway
API Gateway patterns (Kong, Traefik, AWS API Gateway) — rate limiting, auth, routing, versioning. Use when implementing API gateway, reverse proxy, or API management.
Works with
---
name: api-gateway
description: API Gateway patterns (Kong, Traefik, AWS API Gateway) — rate limiting, auth, routing, versioning. Use when implementing API gateway, reverse proxy, or API management.
license: MIT
---
# API Gateway — Kong, Traefik, Patterns
API Gateway moderne pour routing, auth, rate limiting, observabilité.
## Responsabilités
| Fonction | Outils |
|----------|--------|
| **Routing** (path, header, canary) | Kong, Traefik, Nginx |
| **Auth** (JWT, OAuth2, API keys) | Kong plugins, Traefik middleware |
| **Rate Limiting** (per-user/IP) | Redis-backed counters |
| **Load Balancing** | HAProxy, Traefik |
| **Circuit Breaker** | Resilience4j, Istio |
## Stacks
**Kong** — Enterprise, plugins riches, K8s-native
**Traefik** — Cloud-native, auto-discovery
**AWS API Gateway** — Managed, serverless
**Nginx** — Performance max, self-hosted
**Envoy** — Service mesh (Istio), gRPC
## Kong Config
```yaml
services:
- name: payment-api
url: http://payment:8080
routes: [{ paths: ["/api/payments"] }]
plugins: [rate-limiting, jwt, prometheus]
```
## Traefik Config
```yaml
http:
routers:
payment:
rule: "PathPrefix(`/api/payments`)"
middlewares: [rate-limit, auth]
middlewares:
rate-limit:
rateLimit: { average: 100, burst: 50 }
```
## Rate Limiting Algorithms
**Fixed Window** — Simple counter, bursty
**Sliding Window** — Rolling counter, lissé
**Token Bucket** — Flexible, burst toléré
**Leaky Bucket** — Output constant, strict
---
Pour setup : `@devops-engineer`More API Design skills
lark-event
larksuite/cli
Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM messages/reactions/chat changes, Approval status changes, Task updates, VC meeting started/joined/ended, Minutes generated, Whiteboard updated, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.
lark-contact
larksuite/cli
飞书 / Lark 通讯录:按姓名 / 邮箱解析成 open_id,或按 open_id 反查姓名 / 部门 / 邮箱 / 联系方式 / 个人状态 / 签名,以及按关键词搜索当前用户可见的机器人 / 智能体(agent)。当用户提到一个名字要下一步发消息 / 排日程,或拿到 open_id 想查具体信息时使用。不负责部门树遍历、按部门列员工、组织架构图,这类需求走原生 OpenAPI。
lark-openapi-explorer
larksuite/cli
飞书/Lark 原生 OpenAPI 探索:从官方文档库中挖掘未经 CLI 封装的原生 OpenAPI 接口。当用户的需求无法被现有 lark-* skill 或 lark-cli 已注册命令满足,需要查找并调用原生飞书 OpenAPI 时使用。

