🔌 API Request Pipeline
An animated REST API pipeline: requests flow from client through an API gateway, an auth check, a versioned backend service and a database — with live 401 and 429 rejections.
Requests travel from a client through an API gateway, an authentication check, a versioned backend service and a database — colour-coded by HTTP method, with live 401 and 429 rejections when auth or rate limits fail.
🔬 What It Demonstrates
The gateway enforces authentication and rate limiting before any request reaches business logic; requests are routed to a v1 or v2 backend depending on the selected API version, then read or write through to a database.
🎮 How to Use
Pick an HTTP method and API version, set the request rate and rate limit, and toggle whether an API key is required. Watch packets succeed, get throttled with 429, or rejected with 401 in real time.
💡 Did You Know?
API versioning strategies like path-based versioning (/v1/, /v2/) let providers evolve an API's behaviour without breaking clients still integrated against an older contract.
An animated REST API pipeline: requests flow from client through an API gateway, an auth check, a versioned backend service and a database — with live 401 and 429 rejections.
3D · Three.js / WebGL renderer · 60 FPS target · runs fully client-side, no install