Google Cloud · Data & Analytics
GCP Event-Driven Data Pipeline
GKE publishing events to Pub/Sub, processed by Cloud Functions into BigQuery. This diagram is written in ArchLex and passes Google Cloud provider checks.
Diagram and source
provider gcp
direction LR
gke -[publishes]-> pubsub
pubsub -[invokes]-> cloud-functions
cloud-functions -[writes]-> bigqueryWhat is in this diagram.
Resources
- Google Kubernetes Engine Google Kubernetes Engine
- Pub/Sub Pub/Sub
- Cloud Functions Cloud Functions
- BigQuery BigQuery
Relationships
- Google Kubernetes Engine publishes Pub/Sub
- Pub/Sub invokes Cloud Functions
- Cloud Functions writes BigQuery
Render it yourself.
Save the source as gcp-event-pipeline.arch and render it with the CLI, or ask your agent to adapt it through the ArchLex MCP server.
npx @archlex/cli render gcp-event-pipeline.arch --output gcp-event-pipeline.svgRelated examples.
- Event-Driven Data Ingestion PipelineHigh-throughput event streaming with API Gateway, EventBridge, SNS, SQS, Lambda workers, DynamoDB, and S3 Data Lake
- Serverless Data Lake ETL PipelineKinesis Firehose streaming to S3 Data Lake, Glue ETL transforming data, and Athena querying results
- Modern Data Warehouse with DataflowPub/Sub streaming to Dataflow for transformation, loading into BigQuery, visualized by Looker
- GCP Serverless Cloud Run + Cloud SQLCloud Run service connected to a Cloud SQL database