Webinar Slides

© 2020, Amazon Web Services, Inc. or its Affiliates. Building a queuing system to control traffic • Protect website (or mobile APP) by allowing limited users to enter • For those users who beyond the online limit, system will place them on waiting list, and direct them to a waiting page • Detect and deactivate idle users from website to release the online positions • Direct waiting users to website from waiting list by "first-in, first-out" mechanism

• 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!