This document discusses how Amazon achieved business agility through continuous delivery practices like frequent releases, automated testing, immutable infrastructure, and treating infrastructure as code. It emphasizes reducing waste and failure through resiliency, visibility, and immunity enabled by cloud services. Continuous delivery is achieved through automation at all stages from building to deploying to monitoring. The future directions discussed are taking these practices further with microservices, Docker/LXC containers, and generating new projects and deploying them with a single click.
5. So… Why boring?
• Multiple release per week
• 5 minute deployments to prod
• Single click environment builds
“If it hurts, do it more often” – Jez Humble
So now it’s all a bit
6. What does agility mean
For technology, we need to be more
effective
- It’s all about building better brakes
For business, the world it’s a changing
- The winners will be the people who can constantly learn and adapt
7. Why cloud and in particular AWS
Cost is a factor, but…
Its all about REDUCING waste
8. It’s ok to fail. Deal with it.
Your infrastructure and apps need resiliancy, visibility and immunity
27. Mixed platform ecosystems
Amazon is not just for bespoke Rails Apps
You need to know when to compromise
How can we leverage AWS
capabilities and services for COTS
29. Challenges with COTS products
Hard
coded
server
lists
Non-‐disposable
servers
Product
configura7on
not
always
scriptable
Presenta7on
informa7on
in
footer