Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
How build and deployment  should shape software      architecturesMatthew Skelton CEng | thetrainline.com IASA UK Ignite 2...
Systems engineering      (robotics, control theory, sensors, neuroscience)            Software          development(financ...
architecture= f (build & deploy)                (for some systems)
“HERESY!”
RELIABLEREPEATABLE  RAPIDRECURRING
Web-basedFrequently- changingPublic-facingHigh-volume
‘R-R-R-R’BUILD AND DEPLOYMENTHelps to avoid the Ball of Mud
BUILDABLESmall pipelined builds on generic build machines         Seconds, not minutes or hours              Short feedbac...
TESTABLETest (separation, harnesses, points)         IDENTIFIABLE  Meaningful versions, packages,  defined dependencies, a...
DEPLOYABLE   Rapid, scriptable, simple failure modes              MONITORABLE    Logging, metrics, transaction tracing    ...
INSTANTIABLE   No snowflakes or singletons        RECOVERABLE No nasty zombies after failuresMTTR more important than MTBF...
RELIABLEREPEATABLE  RAPIDRECURRING
Lightweight, Testable,     Monitorable,     Configurable,Recoverable, Identifiablecomponent architecture
LOAD BALANCING  HIGH AVAILABILITY       SCALINGELASTIC ARCHITECTURES   RAPID RECOVERY
architecture= f (build & deploy)                                                                                          ...
How build and deployment should shape software architectures
How build and deployment should shape software architectures
How build and deployment should shape software architectures
How build and deployment should shape software architectures
How build and deployment should shape software architectures
You’ve finished this document.
Download and read it offline.
Upcoming SlideShare
How build and deploy shapes software architecture at thetrainline.com
Next
Upcoming SlideShare
How build and deploy shapes software architecture at thetrainline.com
Next
Download to read offline and view in fullscreen.

Share

How build and deployment should shape software architectures

Download to read offline

Build and deployment concerns can help us to avoid some architecture anti-patterns, and enable some useful system properties.
Presented at IASA UK Ignite 2 on 10 September 2012 in London.

Related Books

Free with a 30 day trial from Scribd

See all

How build and deployment should shape software architectures

  1. 1. How build and deployment should shape software architecturesMatthew Skelton CEng | thetrainline.com IASA UK Ignite 2, London | #iasaignite 10 September 2012
  2. 2. Systems engineering (robotics, control theory, sensors, neuroscience) Software development(finance, insurance, travel, pharma, media, medical imaging) nowBuild & Deploymentat thetrainline.com @matthewpskelton
  3. 3. architecture= f (build & deploy) (for some systems)
  4. 4. “HERESY!”
  5. 5. RELIABLEREPEATABLE RAPIDRECURRING
  6. 6. Web-basedFrequently- changingPublic-facingHigh-volume
  7. 7. ‘R-R-R-R’BUILD AND DEPLOYMENTHelps to avoid the Ball of Mud
  8. 8. BUILDABLESmall pipelined builds on generic build machines Seconds, not minutes or hours Short feedback cycles (Dan Worthington-Bodart, @danielbodart - http://bit.ly/M85wsX)
  9. 9. TESTABLETest (separation, harnesses, points) IDENTIFIABLE Meaningful versions, packages, defined dependencies, artefact management (think component boundaries)
  10. 10. DEPLOYABLE Rapid, scriptable, simple failure modes MONITORABLE Logging, metrics, transaction tracing CONFIGURABLE Inject settings – no ‘black boxes’ LIGHTWEIGHTKeep things small and easily comprehendible
  11. 11. INSTANTIABLE No snowflakes or singletons RECOVERABLE No nasty zombies after failuresMTTR more important than MTBF* * for most kinds of F
  12. 12. RELIABLEREPEATABLE RAPIDRECURRING
  13. 13. Lightweight, Testable, Monitorable, Configurable,Recoverable, Identifiablecomponent architecture
  14. 14. LOAD BALANCING HIGH AVAILABILITY SCALINGELASTIC ARCHITECTURES RAPID RECOVERY
  15. 15. architecture= f (build & deploy) (for some systems) thank you IASA: www.iasaglobal.org matthewskelton.net | @matthewpskelton Thanks to: Attila S, Jack R and Owain P for feedback. Picture credits: Petra: Wikimedia/Berthold Werner; army engineers: US DoD; ball of mud: pwern.blogspot.co.uk; sports car: xarj.net; zombie: bjj.org; feather: Wikipedia; punch: thelegalblitz.com; passport: coverpalace.com; dogs: reluctantmemsahib.wordpress.com; Meccano: dalefield.com
  • DevTiger

    Apr. 19, 2020
  • matthewskelton

    Sep. 29, 2016
  • Gudimetla

    Sep. 14, 2015
  • asavory

    Sep. 11, 2012

Build and deployment concerns can help us to avoid some architecture anti-patterns, and enable some useful system properties. Presented at IASA UK Ignite 2 on 10 September 2012 in London.

Views

Total views

2,081

On Slideshare

0

From embeds

0

Number of embeds

30

Actions

Downloads

14

Shares

0

Comments

0

Likes

4

×