☁️ SaaS & Cloud · Flowchart
CI/CD Pipeline Flowchart
A typical CI/CD pipeline from a pull request to production: build, tests, security scans, staging deploy, approval and a canary release.
Drawing diagram…
What this diagram shows
- Pull requests must pass tests and scans before merge
- Staging deploy and smoke tests run on every merge
- Production uses a canary release with automatic rollback
Prompt used
CI/CD flowchart: a developer opens a pull request, CI builds the code, runs unit tests, static analysis and dependency security scans. If anything fails the PR is blocked. After review and merge, a container image is built and pushed to the registry, deployed to staging and smoke-tested. After manual approval it goes to production as a 10% canary; if error rates stay normal it is rolled out to 100%, otherwise it is rolled back automatically.
Mermaid code
flowchart TD
A[Developer opens pull request] --> B[Build]
B --> C[Unit tests]
C --> D[Static analysis and security scan]
D --> E{All checks pass?}
E -->|No| F[Block merge, notify developer]
E -->|Yes| G[Code review and merge]
G --> H[Build container image]
H --> I[Push to registry]
I --> J[Deploy to staging]
J --> K[Smoke tests]
K --> L{Manual approval}
L -->|Approved| M[Canary release 10%]
M --> N{Error rate normal?}
N -->|Yes| O[Roll out to 100%]
N -->|No| P[Automatic rollback]Related templates
Kubernetes Microservices Deployment
How a microservices app runs on Kubernetes in the cloud: ingress, namespaces, services with multiple replicas, managed databases and monitoring.
OAuth 2.0 / OpenID Connect Login
The authorization code flow with PKCE used by most modern web and mobile apps to log users in through an identity provider.
Multi-Tenant SaaS Architecture
A B2B SaaS product serving many customer organisations from one platform: tenant-aware services, per-tenant data isolation, billing and admin.
AWS Three-Tier Web Application
The classic three-tier web app on AWS: CloudFront and a load balancer, an autoscaling app tier in private subnets, and a Multi-AZ database.
Event-Driven Architecture with Kafka
Services that talk through events instead of direct calls: an order service publishes events that inventory, payments, notifications and analytics react to.
SaaS Subscription Billing Lifecycle
The states of a SaaS customer's subscription: trial, active, past due with retries, paused, cancelled and expired.