• Email
  • Like
  • Save
  • Private Content
  • Embed
 

Designing for rapid release - Crash & Burn 2012

by on Mar 06, 2012

  • 2,030 views

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 ...

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.

Accessibility

Categories

Upload Details

Uploaded via SlideShare as Adobe PDF

Usage Rights

© All Rights Reserved

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel

9 Embeds 90

http://lanyrd.com 81
http://ferrallasmalaga.blogspot.com 2
http://www.onlydoo.com 1
http://us-w1.rockmelt.com 1
http://lisahparticipationinoccupation.blogspot.co.nz 1
http://lisahparticipationinoccupation.blogspot.com 1
https://twimg0-a.akamaihd.net 1
http://a0.twimg.com 1
http://10.60.60.199 1

More...

Statistics

Likes
7
Downloads
0
Comments
0
Embed Views
90
Views on SlideShare
1,940
Total Views
2,030
Post Comment
Edit your comment

Designing for rapid release - Crash & Burn 2012 Designing for rapid release - Crash & Burn 2012 Presentation Transcript