Lyndsay Prewer Smoothing the continuous delivery path – a tale of two architectures
Short synopsis: What makes Continuous Delivery easy and what makes it hard? Should it be all Scala, Docker and microservices, or is .Net, Windows and monoliths a safer bet? This session shares best practices and anti-patterns encountered by two teams, with very different architectures, both on their journey to successful continuous delivery.
Bio: Lyndsay is an Agile Delivery Consultant. He’s spent the last twenty years helping developers, teams and organisations improve their software delivery. He’s currently consulting for Equal Experts, at HMRC, on the delivery of HMRC’s new Gov.UK digital tax services. He speaks regularly at European conferences (Agile Cambridge, Agile Testing Days, Agile Lean Europe) and London Meetups. For more information, check out lyndsayp.com.
Long synopsis: Continuous Delivery is gaining recognition as a best practice. It’s in use by many leading organisations, including NetFlix, Amazon and Etsy. It’s a proven way of reducing risk, reducing time to market and increasing a team’s agility. Despite these benefits, adopting and improving it is challenging. This is the story of how two very different teams successfully practice and improve Continuous Delivery. Both teams were sizeable (more than five features teams) and mature in their use of agile and lean practices. One team chose Scala, mongodb, Docker and microservices, on a greenfield project. The other faced the constraints of legacy code, .Net, MySQL, Windows, and a monolithic architecture. This session shares the best practices and anti-patterns encountered by the two teams, looking at those common to both, and those that were specific to each team’s own context.