All is not completely rosy in microservice-land. It’s often a sign of an architectural approach’s maturity that anti-patterns begin to be identified and classified alongside well-established principles and practices. Daniel Bryant introduces seven deadly sins from real projects, which left unchecked could easily ruin your next microservices project.
Daniel offers an updated tour for 2016 of some of the nastiest anti-patterns in microservices from several real-world projects he’s encountered as a consultant, providing a series of anti-pattern “smells” you can sniff out and exploring the tools and techniques you need to avoid or mitigate the potential damage.
Daniel Bryant is an independent technical consultant and product architect at Datawire, where he specializes in enabling continuous delivery within organizations through the identification of value streams, the creation of build pipelines, and the implementation of effective testing strategies. Daniel’s technical expertise focuses on DevOps tooling, cloud and container platforms, and microservice implementations. He contributes to several open source projects, writes for InfoQ, O’Reilly, and Voxxed, and regularly presents at international conferences, including OSCON, QCon, and JavaOne.
©2016, O’Reilly UK Ltd • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org