Google Cloud · AI & Machine Learning
E-Commerce Recommendations Engine
Retail API serving product catalog, Recommendations AI generating personalized suggestions to customers. This diagram is written in ArchLex and passes Google Cloud provider checks.
Diagram and source
provider gcp
direction LR
catalog: retail-api["Product Catalog"]
recommendations: recommendations-ai
user_events: pubsub["User Events"]
frontend: cloud-run
cache: memorystore
user_events -[streams]-> recommendations
catalog -[streams]->|catalog feed| recommendations
recommendations -[caches]-> cache
frontend -[reads]-> cache
frontend -[reads]-> catalogWhat is in this diagram.
Resources
- Product Catalog Retail API
- recommendations Recommendations AI
- User Events Pub/Sub
- frontend Cloud Run
- cache Memorystore
Relationships
- User Events streams recommendations
- Product Catalog streams recommendations
- recommendations caches cache
- frontend reads cache
- frontend reads Product Catalog
Render it yourself.
Save the source as gcp-retail-recommendations.arch and render it with the CLI, or ask your agent to adapt it through the ArchLex MCP server.
npx @archlex/cli render gcp-retail-recommendations.arch --output gcp-retail-recommendations.svgRelated examples.
- AI/ML Model Inference PipelineCloudFront and API Gateway feeding Lambda preprocessor to EKS GPU inference cluster backed by ElastiCache and S3
- AI-Powered Document ProcessingDocument AI extracting data from uploads, Natural Language AI analyzing content, stored in Firestore
- GCP Serverless Cloud Run + Cloud SQLCloud Run service connected to a Cloud SQL database
- GCP Event-Driven Data PipelineGKE publishing events to Pub/Sub, processed by Cloud Functions into BigQuery