The Seven Deadly Sins of Microservices

on YouTube ↗50m

" summary

Seven concrete anti‑patterns and actionable fixes: chasing the latest tech like Docker/Kubernetes or Cassandra without evaluation; avoiding service virtualization by using Hoverfly (captures HTTP, injects delays/faults, used to run large load tests); suffering communication lock‑in via shared domain models or API gateway scripts that hide business logic; ignoring non‑functional requirements (use Gatling, Flood.io, OWASP Dependency Check, Clair, Docker Bench); and practicing chaos testing with the simian army plus circuit breakers. Each sin names the tool, the failure mode, and a practical mitigation.

AI-written summary · about

" chapters (9)

1. 0:00Intro
2. 2:14EVALUATION - ARE MICROSERVICES A GOOD FIT?
3. 13:57THE ESB IS DEAD - LONG LIVE THE API GATEWAY!
4. 18:57GETTING LAZY WITH NON-FUNCTIONAL REQUIREMENTS
5. 22:22TESTING NERS IN THE BUILD PIPELINE
6. 27:24PEOPLE PAIN POINT - HOW DOES DEVOPS FIT INTO THIS?
7. 32:40DEVOPS - DEFINE RESPONSIBILITIES
8. 41:53SERVICE VIRTUALISATION / API SIMULATION
9. 47:38THE SEVEN (MORE) DEADLY SINS OF MICROSERVICES

" related talks

• 40m10 tips for failing at microservicesDavid Schmitz · Voxxed Days Microservices 2018
• 57mEmbracing MicroservicesGrzegorz Piwowarek · GeeCON Prague 2023
• 30mHow to Fail at Building Modern MicroservicesAlasdair Nottingham · Devnexus 2020
• 39m10 Tips for failing at microservicesDavid Schmitz · code.talks 2017
• 46mTop 5 techniques for building the worst microservice system everWilliam Brander · NDC Porto 2023
• 47mEmbracing MicroservicesGrzegorz Piwowarek · JDD 2023
• 41mTop 5 techniques for building the worst microservice system everWilliam Brander · NDC London 2023
• 20m3 reasons why micro-services aren't the miracle cureLisa Mittmann · code.talks 2023