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.