This presentation was recorded at GOTO Aarhus 2012 http://gotocon.com Sam Newman - Technical Consultant at Thoughtworks @samnewman4355 RESOURCES https://twitter.com/samnewman https://www.linkedin.com/in/samnewman http://samnewman.io http://samnewman.io/blog https://github.com/snewman ABSTRACT This talk focuses on the kinds of constraints we should consider when evolving their architecture of our systems in order to enable rapid, frequent release. So much of the conversation about Continuous Delivery focuses on the design of build pipelines, or the nuts and bolts of CI and infrastructure automation. But often the biggest constraint in being able to incrementally roll out new features are the problems in the design of the system itself. I'll be pulling together a series of patterns that will help you identify what to look for in your own systems when moving towards Continuous Delivery. RECOMMENDED BOOKS Sam Newman • Monolith to Microservices • https://amzn.to/2Nml96E https://twitter.com/gotocon https://www.facebook.com/GOTOConference http://gotocon.com
Get notified about new features and conference additions.