Smoothing the continuous delivery path: A tale of two teams
Continuous delivery is gaining recognition as a best practice, yet adopting and iteratively improving it is challenging. Lyndsay Prewer shares various best practices for doing continuous delivery well, drawn from his experiences working with two very different organizationsone with a .Net monolith architecture, the other with a microservice architecture of over 300 Scala microservices.
| Talk Title | Smoothing the continuous delivery path: A tale of two teams |
| Speakers | Lyndsay Prewer (Lyndsayp Ltd / Equal Experts) |
| Conference | O’Reilly Software Architecture Conference |
| Conf Tag | Engineering the Future of Software |
| Location | New York, New York |
| Date | April 3-5, 2017 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
Continuous delivery is gaining recognition as a best practice. It is now in use by many leading organizations, including Netflix, Amazon, and Etsy. Yet despite offering a proven way of reducing risk, reducing time to market, and increasing a team’s agility, adopting and improving continuous delivery is challenging. Lyndsay Prewer offers an experience report of the best practices from two very different teams that successfully practice and improve their 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. Lyndsay shares the best practices and pain points encountered by the two teams, looking at those common to both and those that were specific to each team’s own context.
