Webinar Slides

© 2020, Amazon Web Services, Inc. or its Affiliates. What are our challenges? • Unpredictable traffic peaks on both shopping website and mobile APP • Triggered by marketing activities / promotions • Triggered by releasing hot and limited items • Limited capacity on concurrent users due to the performance bottlenecks on application and servers • Scaling up servers to serve all users at the same time may not cost effective • Poor customer experience due to traffic peaks and led to server down • High drop-off rate • Lost sales

• Slide Number 1
• Agenda
• Retailers face challenges in ecommerce
• Challenges continue as more consumers shop online
• Ecommerce: it's hard (and it's getting harder)
• E-commerce : it's hard (and it's getting harder)
• Three Common Scenarios and How We Can Address Them
• Scenario One Quickly migrate your on-premise eCommerce platform to AWS without application change
• Typical ecommerce architecture
• Slide Number 10
• AWS Case Study: Mydress
• Mydress's Solution with AWS
• Mydress's Outcomes
• Scenario Two: Architecture principles for next-gen ecommerce
• Scale: legacy ways of solving it
• Scenario TwoNext-generation ecommerce on AWS
• Migrate and free-up IT resources
• Continuous Improvement and Optimizations
• Scenario Three
• Virtual Waiting Room Reference Architecture
• Scalable Registration System Architecture
• Slide Number 22
• Customer Sharing
• Table of contents
• What is Ztore?
• What are our challenges?
• What are our challenges? (1)
• How can we solve the problem?
• Building a queuing system to control traffic
• How it works?
• Architecture of Ztore queuing system
• Why we choose AWS?
• Benefits of using AWS services to build queuing system
• Benefits of using AWS services to build queuing system (1)
• Benefits of using AWS services to build queuing system (2)
• Q & A
• Thank You!