The Seven More Deadly Sins of Microservices

Explore the pitfalls of microservices architecture in this 48-minute conference talk from GOTO Chicago 2017. Delve into seven common anti-patterns encountered in real-world microservices projects, presented by Daniel Bryant, author of "Containerizing Continuous Delivery in Java." Learn about crucial evaluation techniques, including assessing microservices fit, using the Spine Model for technology evaluation, and understanding the gap between architecture expectations and operational realities. Examine communication challenges, the evolving role of API gateways, and the importance of non-functional requirements. Discover insights on testing, DevOps integration, and effective data store selection. Gain valuable knowledge on context mapping, event storming, and service virtualization to enhance your microservices implementation. This talk provides essential guidance for developers and architects looking to avoid common mistakes and optimize their microservices architecture.

Intro
EVALUATION - ARE MICROSERVICES A GOOD FIT?
EVALUATION OF TECH - THE SPINE MODEL
ARCHITECTURE/OPS. EXPECTATIONS VERSUS REALITY
EVALUATION - BEWARE OF BIAS AND HEURISTICS
DELEGATION OF COMMS OPERABILITY
RPC - NOT THE DEVIL IN DISGUISE
THE ESB IS DEAD - LONG LIVE THE ESB!
THE ESB IS DEAD - LONG LIVE THE API GATEWAY!
GETTING LAZY WITH NON-FUNCTIONAL REQUIREMENTS
TESTING NERS IN THE BUILD PIPELINE
PEOPLE PAIN POINT - HOW DOES DEVOPS FIT INTO THIS?
DEVOPS - THE FULLSTACK ENGINEER MYTH
DEVOPS - DEFINE RESPONSIBILITIES
PREVIOUSLY - ONE MODEL TO RULE THEM ALL
CONTEXT MAPPING (STATIC) & EVENT STORMING (DYNAMIC)
CHOOSE (AND USE) DATA STORES APPROPRIATELY
SERVICE VIRTUALISATION / API SIMULATION
HOVERFLY-JAVA (JUNIT SUPPORT)
THE SEVEN (MORE) DEADLY SINS OF MICROSERVICES
BEDTIME READING