donnemartin/system-design-primer

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

Open

#63 opened on Apr 15, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Python (56,208 forks)batch import
help wantedquestion

Repository metrics

Stars
 (348,624 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Research concurrent request handling patterns like optimistic locking, distributed queues, and database sharding. Compare trade offs and propose an efficient solution.
Tech stack
None
Domain
backenddatabase
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40