"Problems you’ll face in the microservice world"
summary
Clever Cloud runs 400 microservices and finds the real problems are authentication, configuration, messaging and service sizing not architecture buzzwords. Built a RabbitMQ backbone to duplicate events for analytics and uses Warp 10 for time-series; a homemade reverse proxy failed and was rewritten overnight. Prefer environment variables and immutable deploys for config, and recommend RabbitMQ for event duplication plus JWT or macaroons for auth delegation; avoid tiny chatty services and automate deployments and maintenance.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 2:13Security challenges
- 3:44Microservices necessity
- 5:22Polyglot architecture
- 6:52Targeted scaling
- 7:45Evolution and rewriting
- 8:53Team and architecture
- 10:36Zero trust networks
- 13:37Message-based communication
- 17:36Tools and technologies
- 19:44Right-sizing services
- 23:21Service boundaries
- 25:43Service evolution story
- 28:22Configuration management
- 33:17Authentication issues
- 38:15JWT and Macaroons
- 43:27Maintenance and lifecycle
- 45:34Rewriting for efficiency
- 48:06Conclusion
related talks
38mMicroservices, a bittersweet symphony
43mGo micro with Microservices
01h 01mMicroservices Gone Wrong
48mChallenges in Implementing MicroServices
20m3 reasons why micro-services aren't the miracle cure
35mMicroservices: A Tale of 3 Heroes
49mChallenges in Implementing Microservices
40mKill "Microservices" before its too late
