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
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
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
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
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
* APIs - clouds have APIs, programmable resources\n* Enables "infrastructure as code". Word up DevOps\n* Add intelligence to application hosting environments\n\n
* APIs - clouds have APIs, programmable resources\n* Enables "infrastructure as code". Word up DevOps\n* Add intelligence to application hosting environments\n\n
* APIs - clouds have APIs, programmable resources\n* Enables "infrastructure as code". Word up DevOps\n* Add intelligence to application hosting environments\n\n