Designing For Rapid Release • Sam Newman • GOTO 2012
1,395 views · Published 27 March 2013 · 51:15 · Indexed 30 October 2026
Channel: GOTO Conferences · 2013 · Science & Technology
This presentation was recorded at GOTO Aarhus 2012 http://gotocon.com Sam Newman - Technical Consultant at Thoughtworks @SamNewmanWork 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
More from this channel
-
21:24
Jeff Sutherland & Ken Schwaber at ESE Conference Part II • GOTO 2011
-
51:03
Mature Legacy Seeking New Technology: Extracting Gold from Legacy Code • Dave Thomas • GOTO 2011
-
39:32
Reasons Node.js Submissions Get Rejected by SoundCloud • Phil Calçado • GOTO 2012
-
31:56
Engineering Culture • Alexander Grosse • GOTO 2012
-
2:30
Interview with Brian LeRoux • GOTO 2012
-
5:29
Interview with Simon Brown • GOTO 2012
-
19:00
Interview with Rich Hickey • GOTO 2012
-
23:48
Interview with Don Reinertsen • GOTO 2012