Flowchart template · local export
API Gateway Microservices Mermaid Template
Flowchart showing API gateway routing, auth, rate limiting, and service fan-out. Edit the code below, choose a publish preset, then export without signup, watermark, or cloud upload.
APImicroservicesgateway
Paste or edit Mermaid code
Replace the sample below, or load another example.
Load example
Preparing the local renderer without uploading your diagram.Preparing editor…
Live previewSample preview · Clean Docs
Preparing local editor…
Render & export
Export controls activate after your diagram renders locally.
Flowchart
Mode
Default renderNative MermaidOptimized exportStyled download
Export style
Clean DocsGitHub READMETransparent DocsWarm Editorial✦ ProWhiteboard Sketch✦ ProAurora Noir✦ ProBlueprint✦ ProChampagne✦ ProEmerald Suite✦ ProEditorial✦ Pro
Scale
1x2x4x
Or exact width, e.g. 1200px wide
Output: White · comfortable padding
Size: calculated after render
Filename: mermaid-flowchart-white-2x.png
When to use the API Gateway Microservices template
A left-to-right flowchart of a typical API gateway deployment: the Gateway receives client traffic, runs it through the Auth check and the Rate Limit gate, fans out to the User, Order, and Billing services, each with its own database, while observability captures the rate-limiting signals.
- •Explaining a gateway-based microservices topology to new engineers or in an architecture decision record.
- •Reviewing where authentication, rate limiting, and observability sit relative to your backend services.
- •Giving non-engineers a one-glance map of which service owns which database and external provider.
Template code
The full Mermaid source for this template — copy it into any Mermaid-compatible tool, or edit and export it in the editor above.
flowchart LR
Client[Web / Mobile Client] --> Gateway[API Gateway]
Gateway --> Auth[Auth Check]
Gateway --> Limit[Rate Limit]
Auth --> Users[User Service]
Auth --> Orders[Order Service]
Auth --> Billing[Billing Service]
Users --> UserDB[(User DB)]
Orders --> OrderDB[(Order DB)]
Billing --> Stripe[Payment Provider]
Limit --> Metrics[Observability]How to customize this template
- •Replace the Users, Orders, and Billing service nodes with your actual services and keep one database cylinder per service.
- •Swap the Stripe payment provider node for your real processor, or add more external integrations downstream of Billing.
- •Split the Auth check into separate nodes (token validation, session lookup) if your gateway delegates to an identity service.
- •Add a subgraph around the backend services to mark what lives inside your private network versus the public Gateway.