The Ultimate Guide to API Registration: Boost Your Dev Speed
summary
Marlo’s open-source API registration converts an OpenAPI spec into Gateway configs, running as a GitLab pipeline that targets Kong v3.2 and generates deployable templates. It uses lint/validate/process/apply modules to lint specs, enforce guard rails (min 5 rps), inject defaults, and render Gateway-specific templates. Example: a developer-specified 3 rps is flagged against a 5 rps minimum; rate limits like 3 rps / 40 rpm / 120 rph and 128 MB payload limits are supported, plus OIDC/OAuth2/JWT auth and automatic portal publishing.
AI-written summary · about
chapters (12)
- 0:00API registration intro
- 1:29What is API registration
- 3:34Core capabilities
- 6:24Pipeline modules roles
- 8:32Lint and validate modules
- 10:15Guard rails for governance
- 12:21Process module defaults
- 14:48API authentication security
- 15:51Apply module deployment
- 16:35API first contract design
- 17:39API governance friction
- 18:20Conclusion open-source
related talks
38mAPI Mastery: from the Design to Development
28mAPI Gateway: critical component of your digital architecture
29mKong as a gateway for your Drupal API
24mLeveraging Gateway API for Kubernetes Native API Management
25mAutomating API Governance
32mProject API Forge: Streamlining Dev-First API Lifecycle Management.
19mSecure and accelerate APIs' lifecycle with the OpenAPI specification
25mShould I do my own API Gateway?