GigaOM/Structure 2013: A Look At Dark Architecture With Dave Connors

443 views

Published on

Dyn VP of Technical Operations Dave Connors gave a talk at the 2013 Structure/GigaOM event on the principle behind dark architecture and how it applies to scaling a technology company.

Watch the video and get more info here: http://gigaom.com/2013/06/20/making-it-change-less-scary-using-dark-architecture/

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
443
On SlideShare
0
From Embeds
0
Number of Embeds
24
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

GigaOM/Structure 2013: A Look At Dark Architecture With Dave Connors

  1. 1. Dark Architecture & How to Forklift Upgrade Your Infrastructure with Zero Downtime Dave Connors VP, Technical Operations, Dyn @daveconnors from @DynInc at #structureconf
  2. 2. Problem We Are Trying To Solve Inputs Black Magic (Your Current System Architecture) Outputs Different Black Magic (Your New System Architecture) Inputs Inputs Inputs Outputs Outputs Outputs Scale x10, x102, etc. Performance (t2 - t0) <= (t1 - t0) t1 t2 t0 t0 Coupling Tight -> Loose @daveconnors from @DynInc at #structureconf
  3. 3. Dark Architecture • A way of thinking about, and technical approach to, solving the scale/performance/coupling problem while enabling the business to succeed and keeping (some) of your hair • Break big problems into smaller problems • We stand on shoulders of giants – Fowler, Amazon, Netflix, etc.@daveconnors from @DynInc at #structureconf
  4. 4. High Level of Dark Architecture • Legacy approach: Flag Day Upgrade/Deploy – 3 month project -> 6 months, flag day upgrade – “all hands on deck”, cross fingers, fight fires, FML… • Dark architecture – Prioritize by “flows” through system – Run legacy and dark architectures in parallel – Two inputs, two outputs, throw one away @daveconnors from @DynInc at #structureconf
  5. 5. Legacy Approach: Start Legacy System 100% of functionality enabled 100% of functionality consumed New System 0% of functionality enabled 0% of functionality consumed
  6. 6. Legacy Approach: Flag Day! Legacy System 100% of functionality enabled 0% of functionality consumed New System 100% of functionality enabled 100% of functionality consumed
  7. 7. Legacy Approach: Flag Day! Legacy System 100% of functionality enabled 0% of functionality consumed New System 100% of functionality enabled 100% of functionality consumed
  8. 8. Dark Architecture Approach @daveconnors from @DynInc at #structureconf
  9. 9. Dark Architecture: Start Legacy System 100% of functionality enabled 100% of functionality consumed New System 0% of functionality enabled 0% of functionality consumed
  10. 10. Dark Architecture: Throw One Away Legacy System 100% of functionality enabled 100% of functionality consumed New System 2% of functionality enabled 2% of functionality consumed
  11. 11. Dark Architecture: Shift Flows Legacy System 100% of functionality enabled 98% of functionality consumed New System 2% of functionality enabled 2% of functionality consumed
  12. 12. Dark Architecture: Business Choice Legacy System 100% of functionality enabled 80% of functionality consumed New System 20% of functionality enabled 20% of functionality consumed
  13. 13. Customer impact over elegant system diagrams • Your customers are not paying you to have pretty whiteboards of elegant system architectures • Your customers are paying you to make their pain go away. This gets priority. • Option to continue system migration @daveconnors from @DynInc at #structureconf
  14. 14. Questions? Dave Connors VP, Technical Operations, Dyn @daveconnors from @DynInc at #structureconf

×