Your SlideShare is downloading. ×
Building a Resilient CloudInfrastructure. From Scratch.         by Jeremy Jarvis           Co-founder
“The Brightbox story.”
Overview@jeremyjarvis
Overview• Preface: Who, what etc. @jeremyjarvis
Overview• Preface: Who, what etc.• Chapter 1: Feeling the pain @jeremyjarvis
Overview• Preface: Who, what etc.• Chapter 1: Feeling the pain• Chapter 2: Realising an opportunity @jeremyjarvis
Overview•   Preface: Who, what etc.•   Chapter 1: Feeling the pain•   Chapter 2: Realising an opportunity•   Chapter 3: De...
Overview•   Preface: Who, what etc.•   Chapter 1: Feeling the pain•   Chapter 2: Realising an opportunity•   Chapter 3: De...
Overview•   Preface: Who, what etc.•   Chapter 1: Feeling the pain•   Chapter 2: Realising an opportunity•   Chapter 3: De...
Overview•   Preface: Who, what etc.•   Chapter 1: Feeling the pain•   Chapter 2: Realising an opportunity•   Chapter 3: De...
Preface.@jeremyjarvis
Preface.• Agile cloud infrastructure service @jeremyjarvis
Preface.• Agile cloud infrastructure service• “Multi-zone” (datacentre) architecture @jeremyjarvis
Preface.• Agile cloud infrastructure service• “Multi-zone” (datacentre) architecture• UK-based (HQ in Leeds, DCs in Manche...
Preface.•   Agile cloud infrastructure service•   “Multi-zone” (datacentre) architecture•   UK-based (HQ in Leeds, DCs in ...
Preface.•   Agile cloud infrastructure service•   “Multi-zone” (datacentre) architecture•   UK-based (HQ in Leeds, DCs in ...
Preface.•   Agile cloud infrastructure service•   “Multi-zone” (datacentre) architecture•   UK-based (HQ in Leeds, DCs in ...
Preface.•   Agile cloud infrastructure service•   “Multi-zone” (datacentre) architecture•   UK-based (HQ in Leeds, DCs in ...
Chapter 1: Feeling the Pain@jeremyjarvis
Chapter 1: Feeling the Pain@jeremyjarvis
Chapter 1: Feeling the Pain• Launched Ruby-specific hosting service (Sep 2007) @jeremyjarvis
Chapter 1: Feeling the Pain• Launched Ruby-specific hosting service (Sep 2007)• Acquisition interest (no thanks!) @jeremyj...
Chapter 1: Feeling the Pain• Launched Ruby-specific hosting service (Sep 2007)• Acquisition interest (no thanks!)• Built a...
Chapter 1: Feeling the Pain• Launched Ruby-specific hosting service (Sep 2007)• Acquisition interest (no thanks!)• Built a...
Chapter 1: Feeling the Pain• Launched Ruby-specific hosting service (Sep 2007)• Acquisition interest (no thanks!)• Built a...
Chapter 1: Feeling the Pain• Launched Ruby-specific hosting service (Sep 2007)• Acquisition interest (no thanks!)• Built a...
Chapter 2: Realising an opportunity@jeremyjarvis
Chapter 2: Realising an opportunity@jeremyjarvis
Chapter 2: Realising an opportunity• Limited options in EU/UK @jeremyjarvis
Chapter 2: Realising an opportunity• Limited options in EU/UK• If we’re building this for ourselves why not sell it? @jere...
Chapter 2: Realising an opportunity• Limited options in EU/UK• If we’re building this for ourselves why not sell it?• Gene...
Chapter 2: Realising an opportunity•   Limited options in EU/UK•   If we’re building this for ourselves why not sell it?• ...
Chapter 2: Realising an opportunity•   Limited options in EU/UK•   If we’re building this for ourselves why not sell it?• ...
Chapter 2: Realising an opportunity•   Limited options in EU/UK•   If we’re building this for ourselves why not sell it?• ...
Chapter 3: Design phase@jeremyjarvis
Chapter 3: Design phase@jeremyjarvis
Chapter 3: Design phase• Requirements: @jeremyjarvis
Chapter 3: Design phase• Requirements:  – Geographic redundancy (separate datacentres) @jeremyjarvis
Chapter 3: Design phase• Requirements:  – Geographic redundancy (separate datacentres)  – Resilient network (multiple conn...
Chapter 3: Design phase• Requirements:  – Geographic redundancy (separate datacentres)  – Resilient network (multiple conn...
Chapter 3: Design phase• Requirements:  – Geographic redundancy (separate datacentres)  – Resilient network (multiple conn...
Chapter 3: Design phase• Requirements:  – Geographic redundancy (separate datacentres)  – Resilient network (multiple conn...
Chapter 3: Design phase• Requirements:  – Geographic redundancy (separate datacentres)  – Resilient network (multiple conn...
Chapter 3: Design phase• Requirements:  – Geographic redundancy (separate datacentres)  – Resilient network (multiple conn...
Chapter 3: Design phase• Requirements:  – Geographic redundancy (separate datacentres)  – Resilient network (multiple conn...
Chapter 3: Design phase@jeremyjarvis
Chapter 3: Design phase• Process: @jeremyjarvis
Chapter 3: Design phase• Process:– Consulted, at first. Network infrastructure gurus. @jeremyjarvis
Chapter 3: Design phase• Process:– Consulted, at first. Network infrastructure gurus.– We’re on our own! @jeremyjarvis
Chapter 3: Design phase• Process:– Consulted, at first. Network infrastructure gurus.– We’re on our own!– Hands-on, R&D st...
Chapter 3: Design phase• Process:– Consulted, at first. Network infrastructure gurus.– We’re on our own!– Hands-on, R&D st...
Chapter 3: Design phase• Process:– Consulted, at first. Network infrastructure gurus.– We’re on our own!– Hands-on, R&D st...
Chapter 3: Design phase• Process:– Consulted, at first. Network infrastructure gurus.– We’re on our own!– Hands-on, R&D st...
Chapter 3: Design phase• Process:– Consulted, at first. Network infrastructure gurus.– We’re on our own!– Hands-on, R&D st...
Chapter 3: Design phase@jeremyjarvis
Chapter 3: Design phase• Elements: @jeremyjarvis
Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept) @jeremyjarvis
Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept)– Application/software architecture (evolving, ...
Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept)– Application/software architecture (evolving, ...
Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept)– Application/software architecture (evolving, ...
Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept)– Application/software architecture (evolving, ...
Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept)– Application/software architecture (evolving, ...
Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept)– Application/software architecture (evolving, ...
Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept)– Application/software architecture (evolving, ...
Chapter 4: Let’s build this thing!@jeremyjarvis
Chapter 4: Let’s build this thing!@jeremyjarvis
Chapter 4: Let’s build this thing!• Network provisioning (Transit, Metro links, RIPE  membership) @jeremyjarvis
Chapter 4: Let’s build this thing!• Network provisioning (Transit, Metro links, RIPE  membership)• Buying (negotiating) @j...
Chapter 4: Let’s build this thing!• Network provisioning (Transit, Metro links, RIPE  membership)• Buying (negotiating)• I...
Chapter 4: Let’s build this thing!• Network provisioning (Transit, Metro links, RIPE  membership)• Buying (negotiating)• I...
Chapter 4: Let’s build this thing!• Network provisioning (Transit, Metro links, RIPE  membership)• Buying (negotiating)• I...
Chapter 4: Let’s build this thing!• Network provisioning (Transit, Metro links, RIPE  membership)• Buying (negotiating)• I...
Chapter 4: Let’s build this thing!• Network provisioning (Transit, Metro links, RIPE  membership)• Buying (negotiating)• I...
Chapter 5: It’s alive! @jeremyjarvis
Chapter 5: It’s alive! @jeremyjarvis
Chapter 5: It’s alive!• Nov 2010 - Launched private beta (700 users) @jeremyjarvis
Chapter 5: It’s alive!• Nov 2010 - Launched private beta (700 users)• Iteration (fix bottlenecks, improve resilience) @jer...
Chapter 5: It’s alive!• Nov 2010 - Launched private beta (700 users)• Iteration (fix bottlenecks, improve resilience)• New...
Chapter 5: It’s alive!•   Nov 2010 - Launched private beta (700 users)•   Iteration (fix bottlenecks, improve resilience)•...
Chapter 5: It’s alive!•   Nov 2010 - Launched private beta (700 users)•   Iteration (fix bottlenecks, improve resilience)•...
Chapter 5: It’s alive!•   Nov 2010 - Launched private beta (700 users)•   Iteration (fix bottlenecks, improve resilience)•...
Chapter 5: It’s alive!• Nov 2010 - Launched private beta (700 users)• Iteration (fix bottlenecks, improve resilience)• New...
Chapter 5: It’s alive!• Nov 2010 - Launched private beta (700 users)• Iteration (fix bottlenecks, improve resilience)• New...
Epilogue: What did we learn?@jeremyjarvis
Epilogue: What did we learn?@jeremyjarvis
Epilogue: What did we learn?• Building stuff is hard (but can lead to competitive  advantage) @jeremyjarvis
Epilogue: What did we learn?• Building stuff is hard (but can lead to competitive  advantage)• Be your own customers (unde...
Epilogue: What did we learn?• Building stuff is hard (but can lead to competitive  advantage)• Be your own customers (unde...
Epilogue: What did we learn?• Building stuff is hard (but can lead to competitive  advantage)• Be your own customers (unde...
Epilogue: What did we learn?• Building stuff is hard (but can lead to competitive  advantage)• Be your own customers (unde...
Epilogue: What did we learn?• Building stuff is hard (but can lead to competitive  advantage)• Be your own customers (unde...
Thanks.Any questions?
Upcoming SlideShare
Loading in...5
×

"Building a Resilient Cloud Infrastructure. From Scratch." - Cloud East, 28 July 2012

479

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
479
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of ""Building a Resilient Cloud Infrastructure. From Scratch." - Cloud East, 28 July 2012 "

  1. 1. Building a Resilient CloudInfrastructure. From Scratch. by Jeremy Jarvis Co-founder
  2. 2. “The Brightbox story.”
  3. 3. Overview@jeremyjarvis
  4. 4. Overview• Preface: Who, what etc. @jeremyjarvis
  5. 5. Overview• Preface: Who, what etc.• Chapter 1: Feeling the pain @jeremyjarvis
  6. 6. Overview• Preface: Who, what etc.• Chapter 1: Feeling the pain• Chapter 2: Realising an opportunity @jeremyjarvis
  7. 7. Overview• Preface: Who, what etc.• Chapter 1: Feeling the pain• Chapter 2: Realising an opportunity• Chapter 3: Design phase @jeremyjarvis
  8. 8. Overview• Preface: Who, what etc.• Chapter 1: Feeling the pain• Chapter 2: Realising an opportunity• Chapter 3: Design phase• Chapter 4: Let’s build this thing! @jeremyjarvis
  9. 9. Overview• Preface: Who, what etc.• Chapter 1: Feeling the pain• Chapter 2: Realising an opportunity• Chapter 3: Design phase• Chapter 4: Let’s build this thing!• Chapter 5: It’s alive! @jeremyjarvis
  10. 10. Overview• Preface: Who, what etc.• Chapter 1: Feeling the pain• Chapter 2: Realising an opportunity• Chapter 3: Design phase• Chapter 4: Let’s build this thing!• Chapter 5: It’s alive!• Epilogue: Some conclusions/lessons @jeremyjarvis
  11. 11. Preface.@jeremyjarvis
  12. 12. Preface.• Agile cloud infrastructure service @jeremyjarvis
  13. 13. Preface.• Agile cloud infrastructure service• “Multi-zone” (datacentre) architecture @jeremyjarvis
  14. 14. Preface.• Agile cloud infrastructure service• “Multi-zone” (datacentre) architecture• UK-based (HQ in Leeds, DCs in Manchester) @jeremyjarvis
  15. 15. Preface.• Agile cloud infrastructure service• “Multi-zone” (datacentre) architecture• UK-based (HQ in Leeds, DCs in Manchester)• Small team (still only 10 in total) @jeremyjarvis
  16. 16. Preface.• Agile cloud infrastructure service• “Multi-zone” (datacentre) architecture• UK-based (HQ in Leeds, DCs in Manchester)• Small team (still only 10 in total)• Distributed team (Mainly around Leeds) @jeremyjarvis
  17. 17. Preface.• Agile cloud infrastructure service• “Multi-zone” (datacentre) architecture• UK-based (HQ in Leeds, DCs in Manchester)• Small team (still only 10 in total)• Distributed team (Mainly around Leeds)• Developer/DevOps focused (it’s who we are) @jeremyjarvis
  18. 18. Preface.• Agile cloud infrastructure service• “Multi-zone” (datacentre) architecture• UK-based (HQ in Leeds, DCs in Manchester)• Small team (still only 10 in total)• Distributed team (Mainly around Leeds)• Developer/DevOps focused (it’s who we are)• Profitable (for 4 yrs, built from revenue) @jeremyjarvis
  19. 19. Chapter 1: Feeling the Pain@jeremyjarvis
  20. 20. Chapter 1: Feeling the Pain@jeremyjarvis
  21. 21. Chapter 1: Feeling the Pain• Launched Ruby-specific hosting service (Sep 2007) @jeremyjarvis
  22. 22. Chapter 1: Feeling the Pain• Launched Ruby-specific hosting service (Sep 2007)• Acquisition interest (no thanks!) @jeremyjarvis
  23. 23. Chapter 1: Feeling the Pain• Launched Ruby-specific hosting service (Sep 2007)• Acquisition interest (no thanks!)• Built a good reputation, hosted apps for some large customers @jeremyjarvis
  24. 24. Chapter 1: Feeling the Pain• Launched Ruby-specific hosting service (Sep 2007)• Acquisition interest (no thanks!)• Built a good reputation, hosted apps for some large customers• Systems stable, but became unwieldy and hard for us to manage + we wanted to expand offering @jeremyjarvis
  25. 25. Chapter 1: Feeling the Pain• Launched Ruby-specific hosting service (Sep 2007)• Acquisition interest (no thanks!)• Built a good reputation, hosted apps for some large customers• Systems stable, but became unwieldy and hard for us to manage + we wanted to expand offering• Began looking at existing options, nothing fitted our needs (e.g Eucalyptus) @jeremyjarvis
  26. 26. Chapter 1: Feeling the Pain• Launched Ruby-specific hosting service (Sep 2007)• Acquisition interest (no thanks!)• Built a good reputation, hosted apps for some large customers• Systems stable, but became unwieldy and hard for us to manage + we wanted to expand offering• Began looking at existing options, nothing fitted our needs (e.g Eucalyptus)• Decided to build our own “cloud” (Brightbox NG) @jeremyjarvis
  27. 27. Chapter 2: Realising an opportunity@jeremyjarvis
  28. 28. Chapter 2: Realising an opportunity@jeremyjarvis
  29. 29. Chapter 2: Realising an opportunity• Limited options in EU/UK @jeremyjarvis
  30. 30. Chapter 2: Realising an opportunity• Limited options in EU/UK• If we’re building this for ourselves why not sell it? @jeremyjarvis
  31. 31. Chapter 2: Realising an opportunity• Limited options in EU/UK• If we’re building this for ourselves why not sell it?• Generated lots of internal debate @jeremyjarvis
  32. 32. Chapter 2: Realising an opportunity• Limited options in EU/UK• If we’re building this for ourselves why not sell it?• Generated lots of internal debate• Lack of flexibility with PaaS services @jeremyjarvis
  33. 33. Chapter 2: Realising an opportunity• Limited options in EU/UK• If we’re building this for ourselves why not sell it?• Generated lots of internal debate• Lack of flexibility with PaaS services• We’re good at this stuff + we have awesome team @jeremyjarvis
  34. 34. Chapter 2: Realising an opportunity• Limited options in EU/UK• If we’re building this for ourselves why not sell it?• Generated lots of internal debate• Lack of flexibility with PaaS services• We’re good at this stuff + we have awesome team• Decided to shift development focus @jeremyjarvis
  35. 35. Chapter 3: Design phase@jeremyjarvis
  36. 36. Chapter 3: Design phase@jeremyjarvis
  37. 37. Chapter 3: Design phase• Requirements: @jeremyjarvis
  38. 38. Chapter 3: Design phase• Requirements: – Geographic redundancy (separate datacentres) @jeremyjarvis
  39. 39. Chapter 3: Design phase• Requirements: – Geographic redundancy (separate datacentres) – Resilient network (multiple connections) @jeremyjarvis
  40. 40. Chapter 3: Design phase• Requirements: – Geographic redundancy (separate datacentres) – Resilient network (multiple connections) – Agile network layer (Load Balancing, Cloud IP, Firewall) @jeremyjarvis
  41. 41. Chapter 3: Design phase• Requirements: – Geographic redundancy (separate datacentres) – Resilient network (multiple connections) – Agile network layer (Load Balancing, Cloud IP, Firewall) – Distributed (no SPOF) @jeremyjarvis
  42. 42. Chapter 3: Design phase• Requirements: – Geographic redundancy (separate datacentres) – Resilient network (multiple connections) – Agile network layer (Load Balancing, Cloud IP, Firewall) – Distributed (no SPOF) – Modular (easy to grow, JIT) @jeremyjarvis
  43. 43. Chapter 3: Design phase• Requirements: – Geographic redundancy (separate datacentres) – Resilient network (multiple connections) – Agile network layer (Load Balancing, Cloud IP, Firewall) – Distributed (no SPOF) – Modular (easy to grow, JIT) – Future-proof (IPv6) @jeremyjarvis
  44. 44. Chapter 3: Design phase• Requirements: – Geographic redundancy (separate datacentres) – Resilient network (multiple connections) – Agile network layer (Load Balancing, Cloud IP, Firewall) – Distributed (no SPOF) – Modular (easy to grow, JIT) – Future-proof (IPv6) – Programmable (API, CLI) @jeremyjarvis
  45. 45. Chapter 3: Design phase• Requirements: – Geographic redundancy (separate datacentres) – Resilient network (multiple connections) – Agile network layer (Load Balancing, Cloud IP, Firewall) – Distributed (no SPOF) – Modular (easy to grow, JIT) – Future-proof (IPv6) – Programmable (API, CLI) – Open (easy to get stuff in and out) @jeremyjarvis
  46. 46. Chapter 3: Design phase@jeremyjarvis
  47. 47. Chapter 3: Design phase• Process: @jeremyjarvis
  48. 48. Chapter 3: Design phase• Process:– Consulted, at first. Network infrastructure gurus. @jeremyjarvis
  49. 49. Chapter 3: Design phase• Process:– Consulted, at first. Network infrastructure gurus.– We’re on our own! @jeremyjarvis
  50. 50. Chapter 3: Design phase• Process:– Consulted, at first. Network infrastructure gurus.– We’re on our own!– Hands-on, R&D style, lots of testing, experimentation, iteration @jeremyjarvis
  51. 51. Chapter 3: Design phase• Process:– Consulted, at first. Network infrastructure gurus.– We’re on our own!– Hands-on, R&D style, lots of testing, experimentation, iteration– Investigated competition (what’s good/bad) @jeremyjarvis
  52. 52. Chapter 3: Design phase• Process:– Consulted, at first. Network infrastructure gurus.– We’re on our own!– Hands-on, R&D style, lots of testing, experimentation, iteration– Investigated competition (what’s good/bad)– Access to plenty of kit -set up mini-clouds to hack @jeremyjarvis
  53. 53. Chapter 3: Design phase• Process:– Consulted, at first. Network infrastructure gurus.– We’re on our own!– Hands-on, R&D style, lots of testing, experimentation, iteration– Investigated competition (what’s good/bad)– Access to plenty of kit -set up mini-clouds to hack– John and Neil worked very closely on architecture (daily calls) @jeremyjarvis
  54. 54. Chapter 3: Design phase• Process:– Consulted, at first. Network infrastructure gurus.– We’re on our own!– Hands-on, R&D style, lots of testing, experimentation, iteration– Investigated competition (what’s good/bad)– Access to plenty of kit -set up mini-clouds to hack– John and Neil worked very closely on architecture (daily calls)– Don’t reinvent the wheel (Rubyists!) @jeremyjarvis
  55. 55. Chapter 3: Design phase@jeremyjarvis
  56. 56. Chapter 3: Design phase• Elements: @jeremyjarvis
  57. 57. Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept) @jeremyjarvis
  58. 58. Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept)– Application/software architecture (evolving, iterative) @jeremyjarvis
  59. 59. Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept)– Application/software architecture (evolving, iterative)– Hardware selection: @jeremyjarvis
  60. 60. Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept)– Application/software architecture (evolving, iterative)– Hardware selection: • Border routers (Cisco) @jeremyjarvis
  61. 61. Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept)– Application/software architecture (evolving, iterative)– Hardware selection: • Border routers (Cisco) • Switches (Cisco +) @jeremyjarvis
  62. 62. Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept)– Application/software architecture (evolving, iterative)– Hardware selection: • Border routers (Cisco) • Switches (Cisco +) • Host servers (Dell) @jeremyjarvis
  63. 63. Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept)– Application/software architecture (evolving, iterative)– Hardware selection: • Border routers (Cisco) • Switches (Cisco +) • Host servers (Dell) • Standardised rack design (modular) @jeremyjarvis
  64. 64. Chapter 3: Design phase• Elements:– Network architecture (proof-of-concept)– Application/software architecture (evolving, iterative)– Hardware selection: • Border routers (Cisco) • Switches (Cisco +) • Host servers (Dell) • Standardised rack design (modular)– Datacentre selection (Proximity, Independent, Competing) @jeremyjarvis
  65. 65. Chapter 4: Let’s build this thing!@jeremyjarvis
  66. 66. Chapter 4: Let’s build this thing!@jeremyjarvis
  67. 67. Chapter 4: Let’s build this thing!• Network provisioning (Transit, Metro links, RIPE membership) @jeremyjarvis
  68. 68. Chapter 4: Let’s build this thing!• Network provisioning (Transit, Metro links, RIPE membership)• Buying (negotiating) @jeremyjarvis
  69. 69. Chapter 4: Let’s build this thing!• Network provisioning (Transit, Metro links, RIPE membership)• Buying (negotiating)• Installing kit (Routers, Switches, Servers) @jeremyjarvis
  70. 70. Chapter 4: Let’s build this thing!• Network provisioning (Transit, Metro links, RIPE membership)• Buying (negotiating)• Installing kit (Routers, Switches, Servers)• Use datacentre staff where possible (racking/stacking) @jeremyjarvis
  71. 71. Chapter 4: Let’s build this thing!• Network provisioning (Transit, Metro links, RIPE membership)• Buying (negotiating)• Installing kit (Routers, Switches, Servers)• Use datacentre staff where possible (racking/stacking)• Software development (several applications, iterative) @jeremyjarvis
  72. 72. Chapter 4: Let’s build this thing!• Network provisioning (Transit, Metro links, RIPE membership)• Buying (negotiating)• Installing kit (Routers, Switches, Servers)• Use datacentre staff where possible (racking/stacking)• Software development (several applications, iterative)• Writing configs (again, iterative - infra as code) @jeremyjarvis
  73. 73. Chapter 4: Let’s build this thing!• Network provisioning (Transit, Metro links, RIPE membership)• Buying (negotiating)• Installing kit (Routers, Switches, Servers)• Use datacentre staff where possible (racking/stacking)• Software development (several applications, iterative)• Writing configs (again, iterative - infra as code)• Documentation (wiki, changelogs, code comments) @jeremyjarvis
  74. 74. Chapter 5: It’s alive! @jeremyjarvis
  75. 75. Chapter 5: It’s alive! @jeremyjarvis
  76. 76. Chapter 5: It’s alive!• Nov 2010 - Launched private beta (700 users) @jeremyjarvis
  77. 77. Chapter 5: It’s alive!• Nov 2010 - Launched private beta (700 users)• Iteration (fix bottlenecks, improve resilience) @jeremyjarvis
  78. 78. Chapter 5: It’s alive!• Nov 2010 - Launched private beta (700 users)• Iteration (fix bottlenecks, improve resilience)• New features (Load balancing, Firewall etc) @jeremyjarvis
  79. 79. Chapter 5: It’s alive!• Nov 2010 - Launched private beta (700 users)• Iteration (fix bottlenecks, improve resilience)• New features (Load balancing, Firewall etc)• Billing data (distributed stats collection) @jeremyjarvis
  80. 80. Chapter 5: It’s alive!• Nov 2010 - Launched private beta (700 users)• Iteration (fix bottlenecks, improve resilience)• New features (Load balancing, Firewall etc)• Billing data (distributed stats collection)• “Enterprise” billing software *sad face* @jeremyjarvis
  81. 81. Chapter 5: It’s alive!• Nov 2010 - Launched private beta (700 users)• Iteration (fix bottlenecks, improve resilience)• New features (Load balancing, Firewall etc)• Billing data (distributed stats collection)• “Enterprise” billing software *sad face*• Oct 2011 - General availability (no change really, just £ £) @jeremyjarvis
  82. 82. Chapter 5: It’s alive!• Nov 2010 - Launched private beta (700 users)• Iteration (fix bottlenecks, improve resilience)• New features (Load balancing, Firewall etc)• Billing data (distributed stats collection)• “Enterprise” billing software *sad face*• Oct 2011 - General availability (no change really, just £ £)• Product development (more and better features) @jeremyjarvis
  83. 83. Chapter 5: It’s alive!• Nov 2010 - Launched private beta (700 users)• Iteration (fix bottlenecks, improve resilience)• New features (Load balancing, Firewall etc)• Billing data (distributed stats collection)• “Enterprise” billing software *sad face*• Oct 2011 - General availability (no change really, just £ £)• Product development (more and better features)• Marketing (getting the word out, communication) @jeremyjarvis
  84. 84. Epilogue: What did we learn?@jeremyjarvis
  85. 85. Epilogue: What did we learn?@jeremyjarvis
  86. 86. Epilogue: What did we learn?• Building stuff is hard (but can lead to competitive advantage) @jeremyjarvis
  87. 87. Epilogue: What did we learn?• Building stuff is hard (but can lead to competitive advantage)• Be your own customers (understand market, use products) @jeremyjarvis
  88. 88. Epilogue: What did we learn?• Building stuff is hard (but can lead to competitive advantage)• Be your own customers (understand market, use products)• Don’t *over*estimate competition (look behind the mask) @jeremyjarvis
  89. 89. Epilogue: What did we learn?• Building stuff is hard (but can lead to competitive advantage)• Be your own customers (understand market, use products)• Don’t *over*estimate competition (look behind the mask)• Learn good negotiation (clue: it’s not a battle) @jeremyjarvis
  90. 90. Epilogue: What did we learn?• Building stuff is hard (but can lead to competitive advantage)• Be your own customers (understand market, use products)• Don’t *over*estimate competition (look behind the mask)• Learn good negotiation (clue: it’s not a battle)• All about the launch (could have timed/co-ordinated things better for more “oomph”) @jeremyjarvis
  91. 91. Epilogue: What did we learn?• Building stuff is hard (but can lead to competitive advantage)• Be your own customers (understand market, use products)• Don’t *over*estimate competition (look behind the mask)• Learn good negotiation (clue: it’s not a battle)• All about the launch (could have timed/co-ordinated things better for more “oomph”)• Momentum is important (PR, morale) @jeremyjarvis
  92. 92. Thanks.Any questions?

×