SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
This session will review design principles and considerations when developing your e-commerce solution on AWS. Hear how Popsa, a machine learning start-up, built its e-commerce solution on AWS; and how AO.com, an online retailer of electrical goods, migrated a bespoke e-commerce platform into AWS. Discover what the cultural impact was, and what the future holds.
This session will review design principles and considerations when developing your e-commerce solution on AWS. Hear how Popsa, a machine learning start-up, built its e-commerce solution on AWS; and how AO.com, an online retailer of electrical goods, migrated a bespoke e-commerce platform into AWS. Discover what the cultural impact was, and what the future holds.
4.
Confidential – AWS Cloud Internal/Restricted/Highly Restricted 4
e-commerce Is About Keeping Pace With Fluid
Consumer Behaviours
Recommend
Serve
Use
Evaluate
Receive
Buy
Consider
Tuesday
11:00: Receive digital offer
12:50: Review e-commerce site
12:52: Check product ratings
Thursday
6:37: Research via search engine
7:50: Check consumer blog
Friday
7:26: Visit store to view product
7:38: Inquire with in-store associate
11:00: Post on social
12:50: Submit Product Rating
Saturday
12:50: read packaging
12:50: evaluate design
11:00: Call Contact Centre
12:50: Submit e-mail
Monday
9:00: Text confirmation
2:35: Receive shipment
Saturday
1:45: purchase on e-commerce site
1:46: receive x-sell offer
1:50: share on social
22.
Why Public Cloud?
• Continuing to survive and thrive on
Black Friday
• Leaner/more flexible cost model
• Increased agility, taking the next
step
23.
Why AWS?
• Operational Stability
• Multi-Availability Zone Architecture
• Best service record at the time
• Value Proposition
• Cost optimisation options in our
hands
• Operational agility
• Idempotent infrastructure
• Infrastructure as code
• Reduced lead time to provision
24.
What/How/When
• E-commerce platform
• Feb ‘17 – Aug ’17
• Partnered with Claranet
• Built out cloud competencies
• Terraform / No remote admin access to servers
25.
What benefits realised?
üSuccessful Black Friday
üReduced provisioning lead time from months to minutes
üReplaced our pets with cattle
Halo Effects:
üHigher quality approach to infrastructure (dev-ops)
üCost optimisations
üMore architectural improvements
26.
What benefits realised?
• From ~75 live changes/week
• To ~120 live changes/week
• 99.990+% availability (ours)
• 100% availability (AWS)
0
20
40
60
80
100
120
140
160
180
200
10/01 10/03 10/05 10/07 10/09 10/11 10/01 10/03 10/05 10/07 10/09 10/11 10/01 10/03 10/05 10/07
Deployments Median UCL LCL
27.
What’s next?
• Re-architect some stuff for Lambda/Web API
• Spot instances for QA?
• RDS?
• Continuous Deployment
• Break up monoliths further