Productize Your Services! A Path Towards Effective Microservice Development
summary
Argues that internal services must be treated as products: build a tiny, testable virus-scanner service + broker that exposes a single /scan endpoint, register it in the Cloud Foundry service marketplace, let teams self-service bind instances, measure adoption, then iterate. Shows code-level proof of concept, notes authentication consolidation took ~6 weeks research and ~1 year to first client, warns against two-speed IT and forced adoption, and proposes automating policy checks (eg. Concourse CI license-approval API) so services evolve with real users.
AI-written summary · about
chapters (14)
- 0:00Introduction and journey
- 3:56Agile vs firefighting
- 5:23Lean principles and prototypes
- 7:31User-centered design constraints
- 9:17Platform productization basics
- 11:02Two-speed IT limitations
- 13:30Anti-patterns in service development
- 15:13Client story and Odyssey
- 17:01Code example: Virus scanner
- 21:56Iterative service development
- 22:59Authentication service case
- 24:00Legal compliance as a service
- 25:42Breaking monoliths approach
- 26:48Cultural change and summary
related talks
31mCloud Foundry and Microservices: A Mutualistic Symbiotic Relationship
20mThe Business Benefits of Microservices
54mServices, Services, Everywhere!
45mMicroservices: A retrospective
38mMicroservices, a bittersweet symphony
57mHow Do I Secure My Micro-Services?
44mMicroservices: 5 things I wish I'd known
45mBuilding and evolving microservices: lessons from the frontlines