FlowchartSystem architectureMedium

Microservices overview

High-level view of a microservices system with gateway, services, and shared datastores.

What this diagram shows

Step 01

Gateway fan-out

All client traffic lands on one gateway that routes into the right downstream service.

Step 02

Service isolation

Each domain — auth, orders, payments, search — owns its own service boundary.

Step 03

Shared storage

Services talk to a primary database and a cache layer instead of each other.

About flowchart diagrams

Flowcharts map out a process as boxes and arrows. They work well when you need to explain how a decision, workflow, or pipeline moves from one step to the next.

This template is written in Mermaid — plain text you can edit, version in git, and regenerate the image from any time.

View Mermaid sourcePlain-text diagram syntax — copy or edit directly.

diagram.mmd

1graph LR
2  Client[Client]
3  Gateway[API Gateway]
4  Auth[Auth Service]
5  Orders[Orders Service]
6  Payments[Payments Service]
7  Search[Search Service]
8  DB[(Primary DB)]
9  Cache[(Cache)]
10
11  Client --> Gateway
12  Gateway --> Auth
13  Gateway --> Orders
14  Gateway --> Payments
15  Gateway --> Search
16  Orders --> DB
17  Payments --> DB
18  Search --> Cache

Related templates

More templates that cover similar workflows.

SEQUENCE

Memphis

Client to server data flow

Sequence of calls from a web client through backend services to the database and cache.

System architectureSimple5 nodes

FLOWCHART

Slate

Webhook delivery with retry

Outbound webhook pipeline with signing, retry on failure, and dead-letter fallback.

API workflowMedium8 nodes

FLOWCHART

Brutalist

GitHub Actions release pipeline

CI pipeline running lint, test, build, tag, and publish through GitHub Actions jobs.

CI/CD pipelineMedium7 nodes

FLOWCHART

Memphis

Staged deploy with approval gate

Promote a build through staging, smoke tests, manual approval, and production rollout.

CI/CD pipelineMedium9 nodes