Me, My Organization and My-croservices
summary
Three case studies show concrete wins and failures: one company spins up ad hoc services on Docker Cloud but keeps the old monolith and single database, ends with dozens of small apps that share schema and no monitoring so new code gets polluted; a second replaces an 8‑hour indexing job with an ElasticSearch used as primary DB, sees a temporary 8h→2min proof‑of‑concept but ends up with four tightly coupled services that must be redeployed together and developers forced into ops; a third invests in training, uses Cloud Foundry + API gateway, independent teams and true DevOps and achieves scalable, replaceable services.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:36What are microservices
- 8:20First company’s approach
- 17:18Hype driven development
- 28:39Learning organization
- 37:35Key takeaways
- 40:06Q&A
related talks
45mContinuously delivering containerized, highly available microservices
46mWhy Cross-Functional Teams Build Better Microservices
31mCloud Foundry and Microservices: A Mutualistic Symbiotic Relationship
45mBuilding and evolving microservices: lessons from the frontlines
47mIt is not just Microservices
37mKnee Deep in Microservices
35mSeven years with microservices: a critical review
01h 01mMicroservices Gone Wrong