Wild Microservices and Imaginary DevOps
summary
A large organization built a one-click project generator that scaffolds a new service repository, Jenkins CI, Bitbucket hooks, Jira ticket, initial database schemas and indices, Spring starters and lazybones templates, and pushes Docker images to Artifactory for deployment to Marathon/Kubernetes with monitoring and tracing headers. The system aims to reduce per-service entropy and onboarding time and to expose service pages with versions and docs; in practice the core pipeline mostly works and speeds teams, but cross-service dependencies, complete infrastructure automation and policy rollouts are still unfinished.
AI-written summary · about
chapters (11)
- 0:00DevOps myths vs realities
- 4:19DevOps maturity
- 6:05Architecture breaks
- 10:16Microservices pros and cons
- 14:11Dev and ops collaboration
- 19:07Container tools history
- 25:12Social barriers and tools
- 26:58Metrics for business
- 28:45Automated deployment
- 31:59DevOps mindset
- 32:21Q&A
related talks
33mEnabling Microservices
39mEnabling Microservices at Orbitz
19mSpeed Up Microservice Setup with Composable Approach
01h 04mDevelop microservices faster with an open source platform
43mStandardizing Microservice Development
44mMicroservices: 5 things I wish I'd known
37mKnee Deep in Microservices
43mDevOps for Mere Mortals