Serverless Architecture

API Gateway and Cloud Run. Scales to zero, which is the whole argument.

Format.puml
Length26 lines
LibraryGoogle Cloud icons

The source

26 lines of PlantUML, and pulls in Google Cloud icons. Copy it, or open the template inside Gnomon and render it as it is.

@startuml
!include <gcp/GCPCommon>
!include <gcp/cloud_api_gateway>
!include <gcp/cloud_run>
!include <gcp/cloud_functions>
!include <gcp/pubsub>
!include <gcp/firestore>
!include <gcp/cloud_scheduler>

title GCP — Serverless architecture

left to right direction

GCP_CLOUD_API_GATEWAY(gw, "API Gateway")
GCP_CLOUD_RUN(run, "Cloud Run", "container service")
GCP_PUBSUB(ps, "Pub/Sub", "events")
GCP_CLOUD_FUNCTIONS(fn, "Cloud Functions", "handler")
GCP_FIRESTORE(fs, "Firestore", "documents")
GCP_CLOUD_SCHEDULER(sched, "Cloud Scheduler", "cron")

gw --> run
run --> ps
ps --> fn
fn --> fs
sched --> fn
@enduml

Render this offline

This template ships in Gnomon and renders on your machine, with no account and nothing sent to a server. The browser editor is free and needs no install.

Get Gnomon Open the browser editor

Others in Google Cloud architecture diagrams

Simple ArchitectureLoad balancer, compute, database. The shape most projects start as.
VPC NetworkingDNS, CDN and the network edge. Draw this when latency or egress is the question.
Microservices (GKE)GKE with a load balancer in front. The heavier option, and sometimes the right one.
Data PlatformPub/Sub into Dataflow. The pipeline shape, where ordering and replay matter.
CI/CD PipelineCloud Build and Artifact Registry. The path from commit to running service.