Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to An agile approach to cloud infrastructure
Similar to An agile approach to cloud infrastructure (20)
More from Richard Seroter
More from Richard Seroter (10)
Recently uploaded
Recently uploaded (20)
An agile approach to cloud infrastructure
- 1. AN AGILE APPROACH TO INFRASTRUCTURE Richard Seroter @rseroter
- 2. Richard Seroter Sr. Director of Product at Pivotal Lead Cloud Editor for InfoQ.com 9-time Microsoft MVP for Integration Technical Trainer at Pluralsight 3-time Book Author
- 3. Team vs. silo orientation
- 5. Delivery team succeeds together
- 6. #1 Review characteristics #2 Discuss org changes #3 See examples
- 8. Elastic Infrastructure On-demand Infrastructure Ephemeral Infrastructure Metered Infrastructure Simple Infrastructure Connected Infrastructure Supported Infrastructure Consistent Infrastructure Miniaturized Infrastructure Abstracted Infrastructure
- 9. Elastic Infrastructure On-demand Infrastructure Ephemeral Infrastructure Metered Infrastructure Simple Infrastructure Connected Infrastructure Supported Infrastructure Consistent Infrastructure Miniaturized Infrastructure Abstracted Infrastructure
- 10. Elastic Infrastructure What Is It? Adapt your allocated infrastructure to current need.
- 11. Elastic Infrastructure Why does it matter? Experiment with quick performance tests Save time by responding to spikes, troughs Save money by scaling tiers independently
- 12. Elastic Infrastructure How to do it? Scale server count (e.g. AWS Autoscale) Scale server instance (e.g. CTL Cloud resize) Scale app pool (e.g. Google Container Engine)
- 13. Elastic Infrastructure On-demand Infrastructure Ephemeral Infrastructure Metered Infrastructure Simple Infrastructure Connected Infrastructure Supported Infrastructure Consistent Infrastructure Miniaturized Infrastructure Abstracted Infrastructure
- 14. On-demand Infrastructure What Is It? Infrastructure available whenever you need it.
- 15. On-demand Infrastructure Why does it matter? Experiment quickly Expand reach via access diverse geographies Realistically test software
- 16. On-demand Infrastructure How to do it? Cloud environment (public or private) Local, virtualized stacks Shared hosts (e.g. running containers or PaaS)
- 17. Elastic Infrastructure On-demand Infrastructure Ephemeral Infrastructure Metered Infrastructure Simple Infrastructure Connected Infrastructure Supported Infrastructure Consistent Infrastructure Miniaturized Infrastructure Abstracted Infrastructure
- 18. Ephemeral Infrastructure What Is It? Infrastructure lives only for short periods.
- 19. Ephemeral Infrastructure Why does it matter? Easily discard unused resources Avoid overburdened, shared environments Minimize expensive monitoring and patching processes
- 20. Ephemeral Infrastructure How to do it? Use immutable infrastructure patterns Make gold images/containers easy to produce and share Provide visibility and tools to prune unused resources
- 21. Elastic Infrastructure On-demand Infrastructure Ephemeral Infrastructure Metered Infrastructure Simple Infrastructure Connected Infrastructure Supported Infrastructure Consistent Infrastructure Miniaturized Infrastructure Abstracted Infrastructure
- 22. Metered Infrastructure What Is It? Pay-per-use based on consumption.
- 23. Metered Infrastructure Why does it matter? Encourage responsible consumption Increase transparency related to operational costs Accelerates transition to automation-driven solutions
- 24. Metered Infrastructure How to do it? Cloud hosting with per- resource billing and visibility Use CI tools that can spin up infrastructure as needed
- 25. Elastic Infrastructure On-demand Infrastructure Ephemeral Infrastructure Metered Infrastructure Simple Infrastructure Connected Infrastructure Supported Infrastructure Consistent Infrastructure Miniaturized Infrastructure Abstracted Infrastructure
- 26. Simple Infrastructure What Is It? Constrained but adequate set of infrastructure choices.
- 27. Simple Infrastructure Why does it matter? Focus on innovation, not debating hardware options Staff doesn’t have to remember unique setups
- 28. Simple Infrastructure How to do it? Set up catalog of preferred configurations in cloud Focus on key compute dimensions Offer channel for teams to share upcoming needs
- 29. Elastic Infrastructure On-demand Infrastructure Ephemeral Infrastructure Metered Infrastructure Simple Infrastructure Connected Infrastructure Supported Infrastructure Consistent Infrastructure Miniaturized Infrastructure Abstracted Infrastructure
- 30. Connected Infrastructure What Is It? Infrastructure that is accessible to core services.
- 31. Connected Infrastructure Why does it matter? Avoid wasting time configuring individual access Run a secure, standard setup Accelerate deployments and experimentation
- 32. Connected Infrastructure How to do it? Bridge networks between environments Ensure that shared services (DB, messaging) are accessible Give teams access to push to production
- 33. Elastic Infrastructure On-demand Infrastructure Ephemeral Infrastructure Metered Infrastructure Simple Infrastructure Connected Infrastructure Supported Infrastructure Consistent Infrastructure Miniaturized Infrastructure Abstracted Infrastructure
- 34. Supported Infrastructure What Is It? Infrastructure that’s owned and maintained by the right team.
- 35. Supported Infrastructure Why does it matter? Security and licensing risks from infrastructure sprawl Teams on pooled infrastructure assume support Encourages transition to DevOps
- 36. Supported Infrastructure How to do it? Base images/containers defined with best practices Automation provided for management at scale Modern techniques for ephemeral instances
- 37. Elastic Infrastructure On-demand Infrastructure Ephemeral Infrastructure Metered Infrastructure Simple Infrastructure Connected Infrastructure Supported Infrastructure Consistent Infrastructure Miniaturized Infrastructure Abstracted Infrastructure
- 38. Consistent Infrastructure What Is It? Identical, repeatable configurations across environments.
- 39. Consistent Infrastructure Why does it matter? Save time troubleshooting snowflake servers Empower teams to quickly build standard environments Apply best practices and avoid accidental security holes
- 40. Consistent Infrastructure How to do it? Treat infrastructure as code (e.g. Chef, Ansible) Build environments using evolving, but standard, definitions (e.g. Terraform) Constantly reset environments to avoid “drift”
- 41. Elastic Infrastructure On-demand Infrastructure Ephemeral Infrastructure Metered Infrastructure Simple Infrastructure Connected Infrastructure Supported Infrastructure Consistent Infrastructure Miniaturized Infrastructure Abstracted Infrastructure
- 42. Miniaturized Infrastructure What Is It? Developers using local, production-like environments.
- 43. Miniaturized Infrastructure Why does it matter? Simulate runtime setup on a smaller scale Avoid “works on my machine” problems Accelerate onboarding of new team members
- 44. Miniaturized Infrastructure How to do it? Shared sandboxes On-demand cloud development environments Virtualization templates (e.g. Vagrant)
- 45. Elastic Infrastructure On-demand Infrastructure Ephemeral Infrastructure Metered Infrastructure Simple Infrastructure Connected Infrastructure Supported Infrastructure Consistent Infrastructure Miniaturized Infrastructure Abstracted Infrastructure
- 46. Abstracted Infrastructure What Is It? Remove inherent knowledge of what sits beneath your applications.
- 47. Abstracted Infrastructure Why does it matter? Focus only on application tier Design more portable systems Achieve higher density environments
- 48. Abstracted Infrastructure How to do it? Microservices bundled into containers (e.g. Docker) Use asynchronous, serverless app constructs (e.g. AWS Lambda) Leverage an application platform (e.g. Cloud Foundry)
- 49. Changes Needed
- 56. Project Management Product teams track large infrastructure demands Rarely have line items for building infrastructure
- 57. Finance Clear transparency on infrastructure costs Projected costs factored lightly into business cases for new teams
- 58. Human Resources Hire generalists Incentivize transparent, impactful performance
- 59. Development Familiarity with infrastructure and config management Comfortable with multiple application containers
- 60. Operations Build a solid base platform Help define standard configurations
- 61. #1 Review characteristics #2 Discuss org changes #3 See examples