Deployment and Management in the Age of Cloud Integrated Applications
summary
A runnable Twitter sentiment app is deployed as a multi‑service system using real tools: terraform workspaces create isolated state files and separate resource groups, allowing apply/destroy per instance; a Kubernetes cluster with Open Service Broker and Service Catalog bindings provisions Azure services and writes connection secrets into Kubernetes for pods to consume; CNABs (Porter, Docker App) package everything for install; notes call out secret leakage in state files, varying maturity, and rough edges around workspace UX and plan-to-class mapping.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 0:16Agenda
- 1:46Software Deployment
- 3:27Modern Applications
- 9:51Terraform
- 12:07Terraform State
- 13:32Terraform Configuration
- 19:10Open Service Broker
- 19:53Service Catalog
- 24:18Instance Management
- 26:08Demo
related talks
26mTerraforming Our Tenant: Self-Serving Apps as Code
50mPlatform Engineering: Creating Scalable and Resilient Systems
48mSelf-serve app infrastructure using Azure Deployment Environments
37mModern Architecture in the Cloud of 2026
16mRapidly dev and deploy Spring apps to
17mDeployments We Can Believe In
39mExperiences and Lessons Learned Building a Multi-Cloud Spring Boot Backend
01h 04mDeploying and Scaling Microservices