Curated example · Editable connections
SaaS architecture
you can explore.
Follow a web request through an API, a cache, and a database.
Curated example
Follow the connections.
Sends a request. Treat everything arriving from the browser as untrusted input.
Make it your own
Browser -> API Gateway -> Application API -> PostgreSQL
API Gateway -> Auth Service
Application API -> Redis Cache
Application API -> Background WorkerChecking workspace availability. You can explore and copy this example now.
Read the main request path
Start with Browser → API Gateway → Application API → PostgreSQL. These arrows show intended dependencies. They are not a recording of production traffic. The authentication service, cache, and worker are supporting components, so keep them separate from the main path.
Make the example fit your application
Remove the gateway if the browser calls your application directly. Rename PostgreSQL to your actual datastore. If jobs run through a queue, add that queue between the application and worker. Keep the diagram small enough that someone can follow one request without needing a second explanation.
Review what the picture leaves out
Record where access checks occur, how cache invalidation works, and what happens after a job fails. A three-tier architecture diagram is useful for orientation; it does not prove availability, security, or the correctness of a deployment.
Another system to explore
SaaS architecture
Follow a web request through an API, a cache, and a database.
Explore the diagram02AI agent architecture
See how an orchestrator, model, tools, and memory work together.
Explore the diagram03RAG architecture
Separate document ingestion from retrieval and answer generation.
Explore the diagram