donnemartin/system-design-primer

Efficient method to address concurrent requests in a successfully e-commerce platform

Open

#63 创建于 2017年4月15日

在 GitHub 查看
 (2 评论) (0 反应) (0 负责人)Python (348,624 star) (56,208 fork)batch import
help wantedquestion

描述

Hi,

Given a successfully e-commerce platform like Amazon, when there are millions of sellers and buyers. If a seller is selling many 20 articles and receives 30 concurrent buying request from customers. How will the platform addresses effectively and efficiently all those concurrent requests.

Here is what I thought of: Synchronizing the database for any buying request. The problem here is that we will have some latency and performance issues.

Any Better Solutions. Thanks.

贡献者指南

技术栈
无
领域
backendperformance
议题类型
research
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
concurrency basicsdatabase transactions
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
20
研究方向
This issue asks for a design pattern to handle concurrent purchase requests in an e commerce platform. The repository is a system design primer, so the answer could reference concepts like database isolation levels, optimistic vs pessimistic locking, and message queues. Possible solutions include using a distributed lock or a queue with atomic stock decrement.