The Business Implications of Microservices
summary
Enterprise case studies show concrete moves: a free-text search prototype built in a month and a half proves the microservice split across legacy stacks, Nodejs AWS containers and orchestrators, and convinces boards by demoing faster feature cycles. Operations surface the cost — dozens of services per app (one example ~12) and many more deploys per day — so teams create platform engineering, use CloudTrail for auditability and feature flags for safe rollouts.
AI-written summary · about
chapters (5)
- 0:00Start
- 4:58How Do You Convince Your Boss or Your Business to To Flip the Switch and Move to Micro Service
- 15:34Future Proofing
- 26:21How Are You Dealing with the Challenge of Operations
- 35:28Is Devops a Prerequisite
related talks
26mEnhance System Resilience and Efficiency with Microservices
45mMicroservices: A retrospective
42mMicroservices are Not Worth the Trouble!!??
48mChallenges in Implementing MicroServices
26mPros/Cons of Microservices
25mMaking microservices a behaviour not a buzzword
20mThe Business Benefits of Microservices
54mThe Long Sad History of Microservices
