All is not completely rosy in microservice-land. It is often a sign of an architectural approach’s maturity that in addition to the emergence of well established principles and practices, that anti-patterns also begin to be identified and classified. In this talk we introduce the 2016 edition of the seven deadly sins that if left unchecked could easily ruin your next microservices project …
Target Audience: Developer, Architect
Prerequisites: Basic understanding of microservice principles
This talk will take a tour of some of the nastiest anti-patterns in microservices, giving you the tools to not only avoid but also slay these demons before they tie up your project in their own special brand of hell.
Topics covered include: Pride - selfishly ignoring the new requirements for testing; Envy - introducing inappropriate intimacy within services by creating a shared domain model, or using data stores incorrectly; Wrath - failing to deal with the inevitable bad things that occur within a distributed system, from both the perspective of technology and the organisation; Sloth - getting lazy with the non-functional requirements; and Lust - embracing the latest and greatest technology without evaluating the operational impact incurred by these choices.