Production Blueprints
How it all actually connects
Real dev-to-production setups, diagrammed end to end: which tool talks to which, what each pipeline stage does, where deployments fail, and how to explain it in an interview.
One blueprint is open to read in full. Sign in free to read all 12.
Delivery pipeline
.NET 8 + Angular 20 on Azure Windows VMs
Jenkins builds once in dev and publishes a versioned package to Nexus; Ansible AWX deploys it to IIS on Windows VMs across five environments.
1 diagram · View blueprint →
Delivery pipeline
Docker + Kubernetes: containers from commit to cluster
Jenkins builds and tests in dev, then containerises: Docker build, image pushed to Artifactory, release tagged in Nexus, rolled out to Kubernetes across four environments.
1 diagram · Sign in to read
Cloud DevOps · Azure
DevOps on Azure: Azure DevOps to AKS
The Azure-native path from work item to running container: Boards and Repos, a multi-stage Azure Pipeline, images in ACR, deployment to AKS with environment approvals, and Key Vault and Azure Monitor around it.
2 diagrams · Sign in to read
Cloud DevOps · AWS
DevOps on AWS: CodePipeline to ECS
The AWS-native path from commit to running container: CodePipeline orchestrates CodeBuild and CodeDeploy, images live in ECR and run on ECS Fargate, with a separate AWS account per environment and automatic rollback on CloudWatch alarms.
2 diagrams · Sign in to read
Cloud DevOps · GCP
DevOps on Google Cloud: Cloud Build to GKE
The Google Cloud-native path from commit to cluster: Cloud Build builds, Artifact Registry stores, and Cloud Deploy promotes a release through dev, staging and prod GKE targets with approvals and rollback.
2 diagrams · Sign in to read
GitOps
Containers on Kubernetes with GitOps
CI builds and pushes the image, then Git becomes the source of truth: Argo CD pulls the desired state into the cluster, so every change is a reviewed commit and rollback is a git revert.
1 diagram · Sign in to read
Infrastructure as code
Infrastructure as code with Terraform
Every infrastructure change is a pull request: CI plans it, a person reviews the plan, and only then is it applied, with remote state locking and one state per environment.
2 diagrams · Sign in to read
Networking
Three-tier app network in the cloud
How a request travels from a browser to a database: DNS, CDN and WAF, a load balancer, an app tier in a private subnet, and a data tier with no route to the internet.
1 diagram · Sign in to read
Observability
Observability: metrics, logs and traces
How one incident is found and explained: metrics raise the alert, logs give the detail, traces show where the time went, and Alertmanager makes sure a person is paged.
1 diagram · Sign in to read
Release engineering
Release strategies and rollback
Rolling, blue/green and canary releases compared: how traffic moves, what you watch, and the decision path that ends in either 100% or a rollback.
2 diagrams · Sign in to read
Security
DevSecOps: security gates in the pipeline
Nine steps from a developer's laptop to production, with the security checks that each one adds: secret scan, SAST, dependency and image scanning, vault-injected secrets and DAST.
1 diagram · Sign in to read
Windows infrastructure
Windows enterprise: AD, WSUS and an IIS farm
Active Directory and Group Policy as the identity backbone, WSUS patching in rings, two IIS servers behind a load balancer, and event logs forwarded to one place.
1 diagram · Sign in to read