Hull Digital 19 July 2012

1. “Cloud truths.”
Jeremy Jarvis
Co-founder

2. About Brightbox.
@jeremyjarvis

3. About Brightbox.
• Cloud infrastructure service
@jeremyjarvis

4. About Brightbox.
• Cloud infrastructure service
• “Multi-zone” (datacentre) architecture
@jeremyjarvis

5. About Brightbox.
• Cloud infrastructure service
• “Multi-zone” (datacentre) architecture
• Local (HQ in Leeds, DCs in Manchester)
@jeremyjarvis

6. About Brightbox.
• Cloud infrastructure service
• “Multi-zone” (datacentre) architecture
• Local (HQ in Leeds, DCs in Manchester)
• Small team (still only 10 in total)
@jeremyjarvis

7. About Brightbox.
• Cloud infrastructure service
• “Multi-zone” (datacentre) architecture
• Local (HQ in Leeds, DCs in Manchester)
• Small team (still only 10 in total)
• Distributed team (Mainly around Leeds)
@jeremyjarvis

8. About Brightbox.
• Cloud infrastructure service
• “Multi-zone” (datacentre) architecture
• Local (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

9. About Brightbox.
• Cloud infrastructure service
• “Multi-zone” (datacentre) architecture
• Local (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

10. Cloud truths.
It’s about agility.

11. OK, I get it: “agility”...
What does that actually mean?

12. Let’s take a closer look...
@jeremyjarvis

13. Let’s take a closer look...
@jeremyjarvis

14. Let’s take a closer look...
• Automation
@jeremyjarvis

15. Let’s take a closer look...
• Automation
• Portability
@jeremyjarvis

16. Let’s take a closer look...
• Automation
• Portability
• Ease of consumption
@jeremyjarvis

17. Let’s take a closer look...
• Automation
• Portability
• Ease of consumption
• Efficiency
@jeremyjarvis

18. Let’s take a closer look...
• Automation
• Portability
• Ease of consumption
• Efficiency
• Resilience
@jeremyjarvis

19. Automation.
@jeremyjarvis

20. Automation.
@jeremyjarvis

21. Automation.
• APIs - programmable resources (beware
“clouds” without APIs!)
@jeremyjarvis

22. Automation.
• APIs - programmable resources (beware
“clouds” without APIs!)
• "Infrastructure as code" (DevOps)
@jeremyjarvis

23. Automation.
• APIs - programmable resources (beware
“clouds” without APIs!)
• "Infrastructure as code" (DevOps)
• Add intelligence to application hosting
environments
@jeremyjarvis

24. Mobility/Portability.
@jeremyjarvis

25. Mobility/Portability.
@jeremyjarvis

26. Mobility/Portability.
• If you describe your app infrastructure as
code, your apps become more portable
@jeremyjarvis

27. Mobility/Portability.
• If you describe your app infrastructure as
code, your apps become more portable
• Find best value suppliers (not cheapest)
@jeremyjarvis

28. Mobility/Portability.
• If you describe your app infrastructure as
code, your apps become more portable
• Find best value suppliers (not cheapest)
• Avoid lock-in (takes a little effort, use
abstraction libraries?)
@jeremyjarvis

29. Mobility/Portability.
• If you describe your app infrastructure as
code, your apps become more portable
• Find best value suppliers (not cheapest)
• Avoid lock-in (takes a little effort, use
abstraction libraries?)
• Span multiple providers (ultimate in
resilience)
@jeremyjarvis

30. Ease of consumption.
@jeremyjarvis

31. Ease of consumption.
@jeremyjarvis

32. Ease of consumption.
• Immediacy (beware of false clouds)
@jeremyjarvis

33. Ease of consumption.
• Immediacy (beware of false clouds)
• Pay-as-you-go (beware of false clouds)
@jeremyjarvis

34. Ease of consumption.
• Immediacy (beware of false clouds)
• Pay-as-you-go (beware of false clouds)
• No up-front costs (beware of false clouds
where you have to pay up-front)
@jeremyjarvis

35. Ease of consumption.
• Immediacy (beware of false clouds)
• Pay-as-you-go (beware of false clouds)
• No up-front costs (beware of false clouds
where you have to pay up-front)
• Don’t forget to watch what you "eat" (it can
get expensive)
@jeremyjarvis

36. Efficiency.
@jeremyjarvis

37. Efficiency.
@jeremyjarvis

38. Efficiency.
• No capital expenditure
@jeremyjarvis

39. Efficiency.
• No capital expenditure
• On-demand (scale up and down)
@jeremyjarvis

40. Efficiency.
• No capital expenditure
• On-demand (scale up and down)
• Don't need to run your own datacentre/
hardware
@jeremyjarvis

41. Efficiency.
• No capital expenditure
• On-demand (scale up and down)
• Don't need to run your own datacentre/
hardware
• Change of focus from maintaining other
“stuff” to optimising app/environment
@jeremyjarvis

42. Resilience.
@jeremyjarvis

43. Resilience.
@jeremyjarvis

44. Resilience.
• Multiple datacentres (beware of false clouds)
@jeremyjarvis

45. Resilience.
• Multiple datacentres (beware of false clouds)
• No such thing as a silver bullet - you have to design for
failure
@jeremyjarvis

46. Resilience.
• Multiple datacentres (beware of false clouds)
• No such thing as a silver bullet - you have to design for
failure
• Don’t “outsource” - be in control
@jeremyjarvis

47. Thanks.
Any questions?