Session Name: Five Signs You’ve DevOps’d Your Microservices Wrong
This talk is based on some positive and negative experiences I’ve had over the last few years implementing DevOps pipelines for not-so-perfect microservice implementations. It outlines five major anti-patterns that we can stumble on and suggests ways to avoid or repair them to achieve the desired success levels: (1) lack of proper CI/CD: without heavy automation, you will never succeed with microservices, (2) lack of automated testing: things move too quickly with microservices; you will never keep up doing manual testing, (3) constant breaking changes: if one service constantly breaks others, you have not achieved the loose coupling needed to succeed, (4) manual processes or approvals: like testing, other human bottlenecks will stifle your ability to deliver at the pace you need, and (5) monolithic coupling: have you ended up with a “microlith” instead of independently deliverable software elements?
Richard Mills has more than 25 years of experience in software engineering with a concentration on pragmatic software process and tools. Rich has a specific focus in Agile development methods and is passionate about DevOps, Continuous Integration, and Continuous Delivery. As the Solution Lead for DevOps at Coveros, Rich is dedicated to helping customers build software better, faster and more securely by coaching and mentoring in Agile development methodologies, automating software delivery (builds, tests, and deployment) and integrating strong security measures into development techniques. He has spent his career working in the areas of static and dynamic software analysis tools, configuration management, and continuous integration. Rich currently works as a Sr. DevOps Architect with Coveros and has been with the company since 2010, spending most of his time engaged with customers.