Search for a command or topic.

LOCAL SEARCH · NO DATA LEAVES YOUR BROWSER
Make diagrams

Reviewed examples

Browse approved model runs of the prompt bank, with each diagram's prompt, source, and requirements.

Each example is one agent’s unedited, one-shot answer to a prompt from the repository’s prompt bank, approved after review. It keeps the rendered SVG, the .dgm source, the prompt, and the requirements.json contract the agent wrote before authoring. Review notes flag routing findings that remain. Any of them could be refined further, by asking the agent for changes or by editing in Studio.

Prompts come in three difficulties. Easy and medium prompts describe everyday architectures, and their one-shot diagrams are ready to use as they are. Hard prompts are dense on purpose: they are the benchmark for many interlocking relationships across regions, zones, and failure paths, so some arrow crossings remain.

Same prompts, different models

Dumb Diagrams is not tied to one model. The validator, requirements contract, and layout engine do the checking, so any capable frontier model can produce a meaningful diagram. Runs were made with Codex and Cursor, mostly using OpenAI and Anthropic models. Each card below has a switch between two runs of all 16 prompts:

RunReferencePreferencesOwn contractRouting clean
GPT Luna 6 (max reasoning)16/1616/1616/1611/16
Claude Sonnet 5.5 (low reasoning)16/1616/1616/1612/16

The routing findings that remain are crossings in the hard prompts, plus two backward arrows in Luna’s thumbnail pipeline. Both runs are frozen as regression baselines for the engine.

AWS

AWS static website delivery AWS · 2026-11-05Easy
DIAGRAM
Download original SVG
AWS static website delivery architecture diagram by GPT Luna 6 (max)
AWS static website delivery · GPT Luna 6 (max)
AWS static website delivery architecture diagram by GPT Luna 6 (max)
Prompt
Create a simple AWS static website delivery diagram. Show a website visitor, DNS, a content delivery service, and the bucket that stores the website files.
Download Prompt ↓
DIAGRAM
Download original SVG
AWS static website delivery architecture diagram by Claude Sonnet 5.5 (low)
AWS static website delivery · Claude Sonnet 5.5 (low)
AWS static website delivery architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Create a simple AWS static website delivery diagram. Show a website visitor, DNS, a content delivery service, and the bucket that stores the website files.
Download Prompt ↓
Factory IoT telemetry AWS · 2026-11-05Medium
DIAGRAM
Download original SVG
Factory IoT telemetry architecture diagram by GPT Luna 6 (max)
Factory IoT telemetry · GPT Luna 6 (max)
Factory IoT telemetry architecture diagram by GPT Luna 6 (max)
Prompt
Draw a left-to-right AWS architecture for factory IoT telemetry. A factory sensor fleet sends readings to AWS IoT Core, which routes them to Kinesis Data Streams. A Lambda consumer normalizes each reading and writes time-series data to Amazon Timestream; it also sends threshold alerts to Amazon SNS. An external operations dashboard reads from Timestream. Show the returned telemetry path from Timestream to the dashboard. Keep the sensor fleet and dashboard outside AWS Cloud, and all AWS services inside AWS Cloud. Use automatic layout and add no other services.
Download Prompt ↓
DIAGRAM
Download original SVG
Factory IoT telemetry on AWS architecture diagram by Claude Sonnet 5.5 (low)
Factory IoT telemetry on AWS · Claude Sonnet 5.5 (low)
Factory IoT telemetry on AWS architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Draw a left-to-right AWS architecture for factory IoT telemetry. A factory sensor fleet sends readings to AWS IoT Core, which routes them to Kinesis Data Streams. A Lambda consumer normalizes each reading and writes time-series data to Amazon Timestream; it also sends threshold alerts to Amazon SNS. An external operations dashboard reads from Timestream. Show the returned telemetry path from Timestream to the dashboard. Keep the sensor fleet and dashboard outside AWS Cloud, and all AWS services inside AWS Cloud. Use automatic layout and add no other services.
Download Prompt ↓
AWS image thumbnail pipeline AWS · 2026-11-05Medium

Review note: Strict validation reports 2 routing findings, mostly plain arrow crossings; accepted in review.

DIAGRAM
Download original SVG
AWS image thumbnail pipeline architecture diagram by GPT Luna 6 (max)
AWS image thumbnail pipeline · GPT Luna 6 (max)
AWS image thumbnail pipeline architecture diagram by GPT Luna 6 (max)
Prompt
Create an AWS image thumbnail pipeline. An uploader submits an image through an API; the upload handler stores the original and queues a thumbnail job; a processor creates a thumbnail; a content delivery service serves both original and thumbnail images.
Download Prompt ↓
DIAGRAM
Download original SVG
AWS image thumbnail pipeline architecture diagram by Claude Sonnet 5.5 (low)
AWS image thumbnail pipeline · Claude Sonnet 5.5 (low)
AWS image thumbnail pipeline architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Create an AWS image thumbnail pipeline. An uploader submits an image through an API; the upload handler stores the original and queues a thumbnail job; a processor creates a thumbnail; a content delivery service serves both original and thumbnail images.
Download Prompt ↓
AWS document processing AWS · 2026-11-05Hard

Review note: Strict validation reports 15 routing findings, mostly plain arrow crossings; accepted in review.

DIAGRAM
Download original SVG
AWS document processing architecture diagram by GPT Luna 6 (max)
AWS document processing · GPT Luna 6 (max)
AWS document processing architecture diagram by GPT Luna 6 (max)
Prompt
Create an AWS document processing architecture. A document intake client submits documents through API Gateway to a Lambda intake handler, which stores originals in an input S3 bucket and queues jobs in SQS. The jobs queue is consumed by two Fargate workers in two Availability Zones, each in a private subnet of one VPC. Both workers read input S3, write processed files to output S3, update DynamoDB status, and publish completion to SNS. The client downloads outputs through CloudFront, with request flow client -> CloudFront -> output S3 origin. Failed jobs move to a dead-letter queue after the maximum attempts; an operations user inspects the dead-letter queue and DynamoDB and can redrive messages from the DLQ to the jobs queue. SNS sends completion notifications to operations. Keep clients outside AWS and managed services outside the VPC. Show one cloud, one region, one VPC, two AZs, and one private subnet group per AZ. Add no other services.
Download Prompt ↓

Review note: Strict validation reports 12 routing findings, mostly plain arrow crossings; accepted in review.

DIAGRAM
Download original SVG
AWS document processing architecture diagram by Claude Sonnet 5.5 (low)
AWS document processing · Claude Sonnet 5.5 (low)
AWS document processing architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Create an AWS document processing architecture. A document intake client submits documents through API Gateway to a Lambda intake handler, which stores originals in an input S3 bucket and queues jobs in SQS. The jobs queue is consumed by two Fargate workers in two Availability Zones, each in a private subnet of one VPC. Both workers read input S3, write processed files to output S3, update DynamoDB status, and publish completion to SNS. The client downloads outputs through CloudFront, with request flow client -> CloudFront -> output S3 origin. Failed jobs move to a dead-letter queue after the maximum attempts; an operations user inspects the dead-letter queue and DynamoDB and can redrive messages from the DLQ to the jobs queue. SNS sends completion notifications to operations. Keep clients outside AWS and managed services outside the VPC. Show one cloud, one region, one VPC, two AZs, and one private subnet group per AZ. Add no other services.
Download Prompt ↓

Azure

Azure Private Application API Azure · 2026-11-05Easy
DIAGRAM
Download original SVG
Azure Private Application API architecture diagram by GPT Luna 6 (max)
Azure Private Application API · GPT Luna 6 (max)
Azure Private Application API architecture diagram by GPT Luna 6 (max)
Prompt
Create a simple Azure private application API. A client calls API Management, which routes requests to an Azure Function; the function accesses an Azure SQL database through a private endpoint in the application network.
Download Prompt ↓
DIAGRAM
Download original SVG
Azure private application API architecture diagram by Claude Sonnet 5.5 (low)
Azure private application API · Claude Sonnet 5.5 (low)
Azure private application API architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Create a simple Azure private application API. A client calls API Management, which routes requests to an Azure Function; the function accesses an Azure SQL database through a private endpoint in the application network.
Download Prompt ↓
Asynchronous Order Processing Azure · 2026-11-05Medium
DIAGRAM
Download original SVG
Asynchronous Order Processing architecture diagram by GPT Luna 6 (max)
Asynchronous Order Processing · GPT Luna 6 (max)
Asynchronous Order Processing architecture diagram by GPT Luna 6 (max)
Prompt
Create an Azure asynchronous order processing diagram. A storefront submits orders through an API; an intake function validates each order, queues it for processing, and archives the request. A processor consumes queued orders and archive events, saves completed orders in SQL, and sends processing metrics to Azure Monitor.
Download Prompt ↓
DIAGRAM
Download original SVG
Azure asynchronous order processing architecture diagram by Claude Sonnet 5.5 (low)
Azure asynchronous order processing · Claude Sonnet 5.5 (low)
Azure asynchronous order processing architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Create an Azure asynchronous order processing diagram. A storefront submits orders through an API; an intake function validates each order, queues it for processing, and archives the request. A processor consumes queued orders and archive events, saves completed orders in SQL, and sends processing metrics to Azure Monitor.
Download Prompt ↓
Industrial IoT telemetry Azure · 2026-11-05Medium
DIAGRAM
Download original SVG
Industrial IoT telemetry architecture diagram by GPT Luna 6 (max)
Industrial IoT telemetry · GPT Luna 6 (max)
Industrial IoT telemetry architecture diagram by GPT Luna 6 (max)
Prompt
Create a left-to-right Azure IoT telemetry architecture. An industrial sensor fleet sends readings to Azure IoT Hub. IoT Hub routes readings to Event Hubs for processing and to a Storage Account for a raw archive. An Azure Function App consumes the event stream, normalizes readings, and writes current equipment status to Cosmos DB. An external operations dashboard reads the current status. Nest Azure resources in a subscription, region, and resource group. Add no other services and use automatic routing.
Download Prompt ↓
DIAGRAM
Download original SVG
Azure industrial IoT telemetry architecture diagram by Claude Sonnet 5.5 (low)
Azure industrial IoT telemetry · Claude Sonnet 5.5 (low)
Azure industrial IoT telemetry architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Create a left-to-right Azure IoT telemetry architecture. An industrial sensor fleet sends readings to Azure IoT Hub. IoT Hub routes readings to Event Hubs for processing and to a Storage Account for a raw archive. An Azure Function App consumes the event stream, normalizes readings, and writes current equipment status to Cosmos DB. An external operations dashboard reads the current status. Nest Azure resources in a subscription, region, and resource group. Add no other services and use automatic routing.
Download Prompt ↓
Private Azure Order Processing Azure · 2026-11-05Hard

Review note: Strict validation reports 19 routing findings, mostly plain arrow crossings; accepted in review.

DIAGRAM
Download original SVG
Private Azure Order Processing architecture diagram by GPT Luna 6 (max)
Private Azure Order Processing · GPT Luna 6 (max)
Private Azure Order Processing architecture diagram by GPT Luna 6 (max)
Prompt
Create an Azure private order processing architecture. A public client enters through Front Door and API Management to an App Service API. The API reads and writes Azure SQL through a SQL private endpoint and enqueues work in Service Bus. A Function worker consumes Service Bus work, writes files through a Storage private endpoint, and writes order status to the Azure SQL database through the shared SQL private endpoint. The API and Function read Key Vault and emit telemetry to Azure Monitor. Service Bus work that reaches its retry limit moves to a dead-letter queue; an operations client inspects the DLQ and triggers redrive back to the work queue. Show API and Function VNet integration in an application subnet, and place private endpoints in a data subnet. SQL, Storage, Service Bus, Key Vault, and Monitor are managed services outside the VNet but within one subscription, region, and resource group. Show private endpoint relation direction explicitly. Add no other services.
Download Prompt ↓

Review note: Strict validation reports 21 routing findings, mostly plain arrow crossings; accepted in review.

DIAGRAM
Download original SVG
Azure private order processing architecture diagram by Claude Sonnet 5.5 (low)
Azure private order processing · Claude Sonnet 5.5 (low)
Azure private order processing architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Create an Azure private order processing architecture. A public client enters through Front Door and API Management to an App Service API. The API reads and writes Azure SQL through a SQL private endpoint and enqueues work in Service Bus. A Function worker consumes Service Bus work, writes files through a Storage private endpoint, and writes order status to the Azure SQL database through the shared SQL private endpoint. The API and Function read Key Vault and emit telemetry to Azure Monitor. Service Bus work that reaches its retry limit moves to a dead-letter queue; an operations client inspects the DLQ and triggers redrive back to the work queue. Show API and Function VNet integration in an application subnet, and place private endpoints in a data subnet. SQL, Storage, Service Bus, Key Vault, and Monitor are managed services outside the VNet but within one subscription, region, and resource group. Show private endpoint relation direction explicitly. Add no other services.
Download Prompt ↓

Google Cloud

GCP Customer Record API Google Cloud · 2026-11-05Easy
DIAGRAM
Download original SVG
GCP Customer Record API architecture diagram by GPT Luna 6 (max)
GCP Customer Record API · GPT Luna 6 (max)
GCP Customer Record API architecture diagram by GPT Luna 6 (max)
Prompt
Draw a left-to-right Google Cloud diagram for a small customer-record API.
Show an external web client sending HTTPS requests through Cloud Load
Balancing to a Cloud Run API, which reads and writes customer records in Cloud
SQL. Nest a project and primary region inside a Google Cloud organization, and
place the three Google Cloud services in the region. Keep the client outside
the organization. Do not add other services, and use automatic routing.
Download Prompt ↓
DIAGRAM
Download original SVG
Google Cloud customer-record API architecture diagram by Claude Sonnet 5.5 (low)
Google Cloud customer-record API · Claude Sonnet 5.5 (low)
Google Cloud customer-record API architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Draw a left-to-right Google Cloud diagram for a small customer-record API.
Show an external web client sending HTTPS requests through Cloud Load
Balancing to a Cloud Run API, which reads and writes customer records in Cloud
SQL. Nest a project and primary region inside a Google Cloud organization, and
place the three Google Cloud services in the region. Keep the client outside
the organization. Do not add other services, and use automatic routing.
Download Prompt ↓
GCP Document Processing Google Cloud · 2026-11-05Medium
DIAGRAM
Download original SVG
GCP Document Processing architecture diagram by GPT Luna 6 (max)
GCP Document Processing · GPT Luna 6 (max)
GCP Document Processing architecture diagram by GPT Luna 6 (max)
Prompt
Draw a left-to-right Google Cloud document-processing architecture. A partner
uploads documents through a Cloud Run intake service, which stores original
files in a Cloud Storage source bucket. Object notifications from the source
bucket publish to Pub/Sub; a second Cloud Run service consumes those events,
reads the original file, stores normalized output in a separate Cloud Storage
bucket, and writes processing status and metadata to Cloud SQL. Nest the
project and primary region inside a Google Cloud organization, with all Google
Cloud services in the region. Keep the partner outside the organization. Add
no other services and use automatic routing.
Download Prompt ↓
DIAGRAM
Download original SVG
Google Cloud document processing architecture diagram by Claude Sonnet 5.5 (low)
Google Cloud document processing · Claude Sonnet 5.5 (low)
Google Cloud document processing architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Draw a left-to-right Google Cloud document-processing architecture. A partner
uploads documents through a Cloud Run intake service, which stores original
files in a Cloud Storage source bucket. Object notifications from the source
bucket publish to Pub/Sub; a second Cloud Run service consumes those events,
reads the original file, stores normalized output in a separate Cloud Storage
bucket, and writes processing status and metadata to Cloud SQL. Nest the
project and primary region inside a Google Cloud organization, with all Google
Cloud services in the region. Keep the partner outside the organization. Add
no other services and use automatic routing.
Download Prompt ↓
GCP Webhook Event Pipeline Google Cloud · 2026-11-05Medium
DIAGRAM
Download original SVG
GCP Webhook Event Pipeline architecture diagram by GPT Luna 6 (max)
GCP Webhook Event Pipeline · GPT Luna 6 (max)
GCP Webhook Event Pipeline architecture diagram by GPT Luna 6 (max)
Prompt
Draw a left-to-right Google Cloud webhook event pipeline. A partner sends
webhook events through Cloud Load Balancing to a Cloud Functions ingress
handler. The handler publishes to a Pub/Sub topic; Pub/Sub sends events to
Dataflow for processing. Dataflow writes processed records to BigQuery and raw
event files to Cloud Storage. Keep the partner outside the Google Cloud
organization. Nest the event-processing project and primary region in the
organization, and place all services in the region. Add no other services and
use automatic routing.
Download Prompt ↓
DIAGRAM
Download original SVG
Google Cloud webhook event pipeline architecture diagram by Claude Sonnet 5.5 (low)
Google Cloud webhook event pipeline · Claude Sonnet 5.5 (low)
Google Cloud webhook event pipeline architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Draw a left-to-right Google Cloud webhook event pipeline. A partner sends
webhook events through Cloud Load Balancing to a Cloud Functions ingress
handler. The handler publishes to a Pub/Sub topic; Pub/Sub sends events to
Dataflow for processing. Dataflow writes processed records to BigQuery and raw
event files to Cloud Storage. Keep the partner outside the Google Cloud
organization. Nest the event-processing project and primary region in the
organization, and place all services in the region. Add no other services and
use automatic routing.
Download Prompt ↓
GCP Media Processing Google Cloud · 2026-11-05Hard

Review note: Strict validation reports 4 routing findings, mostly plain arrow crossings; accepted in review.

DIAGRAM
Download original SVG
GCP Media Processing architecture diagram by GPT Luna 6 (max)
GCP Media Processing · GPT Luna 6 (max)
GCP Media Processing architecture diagram by GPT Luna 6 (max)
Prompt
Create a GCP media processing architecture. An external media producer sends uploads through Cloud Load Balancing to a regional Cloud Run ingest service. Ingest writes the input object to Cloud Storage and publishes a job to a global Pub/Sub jobs topic. Two Compute Engine workers in separate regional subnets of one VPC consume jobs. Each worker reads input objects, writes processed objects, updates Cloud SQL job status, and publishes completion to a global Pub/Sub topic. Cloud Run notification service delivers completion to an external operations client. Jobs dead-letter to a second Pub/Sub topic. The operations client can inspect dead letters and deliberately redrive them to the jobs topic. Keep global services at project scope, regional services in their region, and show the organization/project. Do not treat a subnet as an availability zone.
Download Prompt ↓

Review note: Strict validation reports 12 routing findings, mostly plain arrow crossings; accepted in review.

DIAGRAM
Download original SVG
Google Cloud media processing architecture diagram by Claude Sonnet 5.5 (low)
Google Cloud media processing · Claude Sonnet 5.5 (low)
Google Cloud media processing architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Create a GCP media processing architecture. An external media producer sends uploads through Cloud Load Balancing to a regional Cloud Run ingest service. Ingest writes the input object to Cloud Storage and publishes a job to a global Pub/Sub jobs topic. Two Compute Engine workers in separate regional subnets of one VPC consume jobs. Each worker reads input objects, writes processed objects, updates Cloud SQL job status, and publishes completion to a global Pub/Sub topic. Cloud Run notification service delivers completion to an external operations client. Jobs dead-letter to a second Pub/Sub topic. The operations client can inspect dead letters and deliberately redrive them to the jobs topic. Keep global services at project scope, regional services in their region, and show the organization/project. Do not treat a subnet as an availability zone.
Download Prompt ↓

Cloud-agnostic

Customer Record API Cloud-agnostic · 2026-11-05Easy
DIAGRAM
Download original SVG
Customer Record API architecture diagram by GPT Luna 6 (max)
Customer Record API · GPT Luna 6 (max)
Customer Record API architecture diagram by GPT Luna 6 (max)
Prompt
Draw a provider-neutral, left-to-right diagram for a small customer-record
API. Show an external web client sending HTTPS requests through an API gateway
to a customer API service, which reads and writes a customer database. Nest a
production account and primary region inside an application cloud, and place
the three services in the region. Keep the client outside the cloud. Do not add
provider-specific products or other infrastructure; use automatic routing.
Download Prompt ↓
DIAGRAM
Download original SVG
Customer-record API (cloud-neutral) architecture diagram by Claude Sonnet 5.5 (low)
Customer-record API (cloud-neutral) · Claude Sonnet 5.5 (low)
Customer-record API (cloud-neutral) architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Draw a provider-neutral, left-to-right diagram for a small customer-record
API. Show an external web client sending HTTPS requests through an API gateway
to a customer API service, which reads and writes a customer database. Nest a
production account and primary region inside an application cloud, and place
the three services in the region. Keep the client outside the cloud. Do not add
provider-specific products or other infrastructure; use automatic routing.
Download Prompt ↓
Team Project Portal Cloud-agnostic · 2026-11-05Medium
DIAGRAM
Download original SVG
Team Project Portal architecture diagram by GPT Luna 6 (max)
Team Project Portal · GPT Luna 6 (max)
Team Project Portal architecture diagram by GPT Luna 6 (max)
Prompt
Create a provider-neutral architecture for a team project portal. Users reach a load balancer that forwards requests to a portal server. The server reads project data from a database, uses a cache for frequent lookups, and retrieves attachments from object storage. Keep the server, database, and cache in a private network; keep the load balancer and object storage outside it. Use a left-to-right automatic layout and add no other services.
Download Prompt ↓
DIAGRAM
Download original SVG
Team project portal (cloud-neutral) architecture diagram by Claude Sonnet 5.5 (low)
Team project portal (cloud-neutral) · Claude Sonnet 5.5 (low)
Team project portal (cloud-neutral) architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Create a provider-neutral architecture for a team project portal. Users reach a load balancer that forwards requests to a portal server. The server reads project data from a database, uses a cache for frequent lookups, and retrieves attachments from object storage. Keep the server, database, and cache in a private network; keep the load balancer and object storage outside it. Use a left-to-right automatic layout and add no other services.
Download Prompt ↓
Webhook Processing Cloud-agnostic · 2026-11-05Medium
DIAGRAM
Download original SVG
Webhook Processing architecture diagram by GPT Luna 6 (max)
Webhook Processing · GPT Luna 6 (max)
Webhook Processing architecture diagram by GPT Luna 6 (max)
Prompt
Draw a provider-neutral, left-to-right webhook-processing diagram. An external
partner sends webhook events to an API gateway and webhook ingress function.
The ingress function queues events and writes an idempotency key to the event
database. An event processor consumes the queue, stores processed status in
the same database, and archives the payload in object storage. Nest a
production account, primary region, and private network inside an application
cloud. Place the gateway and ingress function together in a webhook-edge
boundary and place the queue, processor, and database in an event-processing
boundary within the network. Keep the payload archive in the region outside
the private network. Do not add other services and use automatic routing.
Download Prompt ↓
DIAGRAM
Download original SVG
Webhook processing (cloud-neutral) architecture diagram by Claude Sonnet 5.5 (low)
Webhook processing (cloud-neutral) · Claude Sonnet 5.5 (low)
Webhook processing (cloud-neutral) architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Draw a provider-neutral, left-to-right webhook-processing diagram. An external
partner sends webhook events to an API gateway and webhook ingress function.
The ingress function queues events and writes an idempotency key to the event
database. An event processor consumes the queue, stores processed status in
the same database, and archives the payload in object storage. Nest a
production account, primary region, and private network inside an application
cloud. Place the gateway and ingress function together in a webhook-edge
boundary and place the queue, processor, and database in an event-processing
boundary within the network. Keep the payload archive in the region outside
the private network. Do not add other services and use automatic routing.
Download Prompt ↓
Order Processing with Recovery Region Cloud-agnostic · 2026-11-05Hard

Review note: Strict validation reports 16 routing findings, mostly plain arrow crossings; accepted in review.

DIAGRAM
Download original SVG
Order Processing with Recovery Region architecture diagram by GPT Luna 6 (max)
Order Processing with Recovery Region · GPT Luna 6 (max)
Order Processing with Recovery Region architecture diagram by GPT Luna 6 (max)
Prompt
Create a cloud-neutral order processing architecture in one cloud account with primary and recovery regions. A public buyer reaches a regional load balancer, which forwards requests to an API server inside the primary private application network and cluster. The database and cache are in the same private network. The API uses them, calls an external payment service, and enqueues work in a regional queue outside the network. Show separate database, cache, and payment response arrows back to the API. The queue feeds a worker server in the application cluster. The worker sends fulfillment to an external warehouse and receives its acknowledgment back; it retries by sending work back to the queue. It also writes order status to the primary database and receipts to object storage outside the network. The primary database replicates to a recovery database inside a recovery network. A recovery application server reads that replica and can serve the buyer through a recovery load balancer. Keep payment and warehouse external, and preserve all directions and containment.
Download Prompt ↓

Review note: Strict validation reports 19 routing findings, mostly plain arrow crossings; accepted in review.

DIAGRAM
Download original SVG
Order processing (cloud-neutral) architecture diagram by Claude Sonnet 5.5 (low)
Order processing (cloud-neutral) · Claude Sonnet 5.5 (low)
Order processing (cloud-neutral) architecture diagram by Claude Sonnet 5.5 (low)
Prompt
Create a cloud-neutral order processing architecture in one cloud account with primary and recovery regions. A public buyer reaches a regional load balancer, which forwards requests to an API server inside the primary private application network and cluster. The database and cache are in the same private network. The API uses them, calls an external payment service, and enqueues work in a regional queue outside the network. Show separate database, cache, and payment response arrows back to the API. The queue feeds a worker server in the application cluster. The worker sends fulfillment to an external warehouse and receives its acknowledgment back; it retries by sending work back to the queue. It also writes order status to the primary database and receipts to object storage outside the network. The primary database replicates to a recovery database inside a recovery network. A recovery application server reads that replica and can serve the buyer through a recovery load balancer. Keep payment and warehouse external, and preserve all directions and containment.
Download Prompt ↓