25 editable reference diagrams
Google Cloud Architecture Diagrams
Explore Google Cloud architectures for web applications, event processing, Kubernetes, analytics and machine learning. Follow the components carrying requests or records and distinguish them from scheduling, identity and deployment controls.
Select the pattern around latency, data volume and operational ownership. Cloud Run, GKE and managed data services solve different parts of a workload. Document service accounts, regional dependencies, quotas and recovery plans when turning a reference into an implementation.
Choose a diagram for your design question
Open a reference to inspect its component flow and trade-offs, then adapt it in the browser-local editor. Manual editing does not require login; AI generation and account storage do.

Google Cloud architecture diagram
Separate routing, runtime and persistence.
5 components · 4 connections
Explore google cloud architecture diagram →
GCP three tier application architecture
Bound application-to-database concurrency.
6 components · 5 connections
Explore gcp three tier application architecture →
Google Kubernetes Engine architecture
Use workload identity for service access.
7 components · 6 connections
Explore google kubernetes engine architecture →
Cloud Run microservices architecture
Treat event consumers as independent services.
6 components · 5 connections
Explore cloud run microservices architecture →
Cloud Run functions architecture
Make event processing idempotent.
5 components · 4 connections
Explore cloud run functions architecture →
Google Cloud API Gateway architecture
Validate identity and resource ownership separately.
5 components · 4 connections
Explore google cloud api gateway architecture →
Apigee API management architecture
Expose intentional API products and policies.
7 components · 5 connections
Explore apigee api management architecture →
Google Cloud Load Balancing architecture
Define readiness before balancing traffic.
6 components · 5 connections
Explore google cloud load balancing architecture →
Google Cloud VPC architecture
Restrict inbound and outbound paths independently.
6 components · 5 connections
Explore google cloud vpc architecture →
Shared VPC architecture
Separate network ownership from application ownership.
5 components · 4 connections
Explore shared vpc architecture →
Google Cloud landing zone architecture
Use project boundaries with explicit governance.
6 components · 5 connections
Explore google cloud landing zone architecture →
Google Cloud hybrid connectivity architecture
Test DNS and routing during link failure.
6 components · 6 connections
Explore google cloud hybrid connectivity architecture →
Google Cloud Pub Sub architecture
Acknowledge only after safe processing.
6 components · 5 connections
Explore google cloud pub sub architecture →
Google Cloud Dataflow architecture
Specify event-time and late-data behavior.
5 components · 4 connections
Explore google cloud dataflow architecture →
Google Cloud Dataproc architecture
Separate job lifecycle from durable data.
5 components · 4 connections
Explore google cloud dataproc architecture →
BigQuery data warehouse architecture
Partition and govern analytical access.
6 components · 5 connections
Explore bigquery data warehouse architecture →
Google Cloud Composer architecture
Keep retries safe across external tasks.
6 components · 5 connections
Explore google cloud composer architecture →
Google Cloud Data Fusion architecture
Validate schema contracts at pipeline boundaries.
5 components · 4 connections
Explore google cloud data fusion architecture →
Google Cloud SQL architecture
Distinguish replica reads from recovery copies.
6 components · 4 connections
Explore google cloud sql architecture →
Google Cloud Spanner architecture
Design keys to avoid write hot spots.
5 components · 4 connections
Explore google cloud spanner architecture →
Google Cloud Bigtable architecture
Row keys control locality and hot spots.
7 components · 5 connections
Explore google cloud bigtable architecture →
Firestore application architecture
Do not rely only on client validation.
7 components · 5 connections
Explore firestore application architecture →
Vertex AI architecture
Separate evaluation from model promotion.
7 components · 6 connections
Explore vertex ai architecture →
Vertex AI RAG architecture
Filter retrieval by verified permissions.
8 components · 7 connections
Explore vertex ai rag architecture →
Google Cloud disaster recovery architecture
Test recovery without damaging production state.
7 components · 5 connections
Explore google cloud disaster recovery architecture →