Infra vs Apps – Where are my Pipelines?
summary
Shows concrete CI/CD tradeoffs: use Jenkins or GitHub Actions/Azure DevOps, run end-to-end tests to gate promotion, and expect pushes pull requests and webhooks to trigger pipelines. Splitting front end and back end creates four common cases (front/back × dev/prod) and triggers grow exponentially as microservices, registries and infra-as-code (example: Terraform) land on Kubernetes. Covers container registries, managed identities, branch protections and the operational cost of certificates and secrets.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:43Monorepo - CD Workflow
- 4:38Backends for Frontends (BFFs)
- 5:08Events and Triggers
- 8:52What About Versioning?
- 9:25Microservices
- 11:29Calculator to Kubernetes
- 13:39CI/CD at Scale - Layers
- 16:15InnerSource Code Examples
- 17:31All the Security Configs
- 20:27Takeaways
related talks
26mIntelligent Deployment Pipelines
39mRemove your Testing Bottleneck with CI/CD Pipelines
48mInfrastructure-Agnostic Continuous Delivery
19mHow to utilize Open Source tools to create CI/CD & DevOps workflows
55mBuild your APIs and DevOps Hybrid Skills
43mEvolutionary Infrastructure Using Pipelines
27mArchitect CI/CD on Enterprise level
45mBecoming a Plumber: Building Deployment Pipelines