Microservice Panel

on YouTube ↗47m

" summary

Conference panel argues containers and automated ops enable microservices but warn they move complexity into contracts, tracing and ops. Typical sizing anecdote is 30–40 services per 5–6 devs and one company reports 300 services with no message docs, which worked for internal teams but raises coupling risk. Recommended practices: API gateway, circuit breakers, caching only when necessary, avoid exposing databases, and apply Swagger + generative contract tests. One‑click or near‑one‑click deploy plus heavy production instrumentation proves crucial.

AI-written summary · about

" chapters (10)

1. 0:00Intro
2. 2:12Introductions
3. 5:10Size of Microservices
4. 6:20Microservices and Data
5. 10:58Polyglot
6. 15:06Coupling
7. 20:29Technology Advice
8. 24:05Traceability
9. 29:56Circuit Breakers
10. 42:02Testing

" related talks

• 43mPanel: Microservices, Where Did It All Go WrongKris Jenkins, James Lewis, Ian Cooper · GOTO Copenhagen 2024
• 01h 05mPanel: Were Microservices a Huge Mistake?Pete Hunt, Nick Schrock, Alexy Khrabrov, William Morgan, Chris Richardson, Kikia Carter · Scale By the Bay 2020
• 37mKnee Deep in MicroservicesÁdám Sándor · MesosCon Europe 2017
• 38mMicroservices, a bittersweet symphonySebastian Sogamoso · RailsConf 2015
• 26mPros/Cons of MicroservicesCassandra Shum · Microservices Day London 2017
• 45mContinuously delivering containerized, highly available microservicesMatthias Noback · Dutch PHP Conference 2017
• 55mMicroservices, Where Did It All Go WrongIan Cooper · NDC London 2025
• 26mCreating a scalable ecosystem of MicroservicesArchanaa Ravikumar, Pooja Subramanian · Apidays LIVE Paris 2020