Why e-commerce tests transactional design in HLD - Scalability Evidence

Scalability Analysis - Why e-commerce tests transactional design

Growth Table: E-commerce Transactional Design Scaling

Users	Transactions/sec	Database Load	System Changes
100 users	10-50	Single DB instance handles writes and reads	Simple ACID transactions, no sharding needed
10,000 users	1,000-5,000	DB CPU and I/O increase, some read replicas added	Introduce connection pooling, caching for reads
1,000,000 users	50,000-100,000	Single DB cannot handle writes, bottleneck at DB	Sharding writes, distributed transactions, async processing
100,000,000 users	5,000,000+	Network and storage bottlenecks, complex consistency	Microservices, event sourcing, CQRS, global data centers

First Bottleneck

In e-commerce transactional design, the first bottleneck is the database write capacity. As users increase, the number of transactions (orders, payments, inventory updates) grows. A single database instance can only handle a limited number of writes per second (usually a few thousand). This causes delays and potential data inconsistency if not managed properly.

Scaling Solutions

• Read Replicas: Offload read queries to replicas to reduce load on primary DB.
• Connection Pooling: Efficiently reuse DB connections to handle more concurrent requests.
• Caching: Use in-memory caches (e.g., Redis) for frequently read data like product info.
• Sharding: Split database by user or order ID to distribute write load across multiple DBs.
• Asynchronous Processing: Use message queues to handle non-critical updates later, reducing immediate DB load.
• Eventual Consistency: Relax strict ACID for some operations to improve scalability.
• Microservices: Separate transactional domains (orders, payments, inventory) for independent scaling.

Back-of-Envelope Cost Analysis

Assuming 1 million users with 100,000 transactions per second:

• Database writes: 100,000 QPS (queries per second) - requires multiple DB shards.
• Storage: Each transaction ~1 KB, daily storage ~8.6 TB (100,000 tx/sec * 1 KB * 86400 sec).
• Network bandwidth: 100,000 tx/sec * 1 KB = ~100 MB/s sustained write bandwidth.
• Cache: To reduce DB reads, cache size ~100 GB for hot product data.
• Servers: Multiple app servers (100+) to handle concurrent users and transactions.

Interview Tip

When discussing e-commerce transactional design scalability, start by identifying the transaction volume and database write limits. Explain how ACID properties affect scaling. Then, describe solutions like sharding and asynchronous processing. Always mention trade-offs between consistency and availability. Use real numbers to show understanding.

Self-Check Question

Your database handles 1,000 QPS. Traffic grows 10x to 10,000 QPS. What do you do first and why?

Answer: The first step is to add read replicas and implement connection pooling to reduce load on the primary database. For writes, consider sharding or asynchronous processing to distribute and delay load. This prevents the DB from becoming a bottleneck and maintains transaction integrity.

Key Result

E-commerce transactional design first breaks at database write capacity as users grow; scaling requires sharding, caching, and asynchronous processing to maintain consistency and performance.

Practice

1. Why is transactional design important in e-commerce systems?

easy

A. It ensures all steps in a purchase either complete fully or not at all.

B. It speeds up the website loading time significantly.

C. It allows users to browse products without logging in.

D. It reduces the number of product categories displayed.

Solution

1. Step 1: Understand transaction purpose in e-commerce

   Transactions ensure that multiple related actions, like payment and order creation, happen together.

2. Step 2: Identify the benefit of transactional design

   This prevents partial updates that could cause errors like double charges or lost orders.

3. Final Answer:

   It ensures all steps in a purchase either complete fully or not at all. -> Option A

4. Quick Check:

   Transaction safety = B [OK]

Hint: Transactions keep all purchase steps together [OK]

Common Mistakes:

• Confusing transaction with website speed
• Thinking transactions only affect browsing
• Assuming transactions reduce product categories

2. Which of the following is the correct sequence to test a transaction in e-commerce?

easy

A. Check payment success, then update order status, then confirm inventory.

B. Update order status, confirm inventory, then check payment success.

C. Confirm inventory, update order status, then check payment success.

D. Confirm inventory, check payment success, then update order status.

Solution

1. Step 1: Understand transaction steps order

   First, confirm inventory is available to fulfill the order.

2. Step 2: Follow with payment and order update

   Then check payment success, and finally update order status to complete.

3. Final Answer:

   Confirm inventory, check payment success, then update order status. -> Option D

4. Quick Check:

   Correct transaction sequence = A [OK]

Hint: Inventory check before payment, then update order [OK]

Common Mistakes:

• Updating order before payment confirmation
• Checking payment before inventory availability
• Skipping inventory confirmation step

3. Consider this simplified transaction test code snippet:

beginTransaction()
if (checkInventory()) {
  if (processPayment()) {
    updateOrderStatus('confirmed')
    commitTransaction()
  } else {
    rollbackTransaction()
  }
} else {
  rollbackTransaction()
}

What happens if processPayment() fails?

medium

A. The transaction is rolled back, no changes saved.

B. Inventory is reduced but payment is not processed.

C. The order status is updated to 'confirmed'.

D. The transaction commits partially.

Solution

1. Step 1: Analyze payment failure branch

   If processPayment() returns false, the code calls rollbackTransaction().

2. Step 2: Understand rollback effect

   Rollback cancels all changes made in the transaction, so no order update or inventory change is saved.

3. Final Answer:

   The transaction is rolled back, no changes saved. -> Option A

4. Quick Check:

   Payment failure triggers rollback = C [OK]

Hint: Failed payment triggers rollback, no partial commit [OK]

Common Mistakes:

• Assuming order status updates despite payment failure
• Thinking inventory changes persist after rollback
• Believing partial commits happen on failure

4. A test for e-commerce transaction fails because orders are duplicated after retry. What is the likely cause?

medium

A. Order status is updated before payment confirmation.

B. Inventory check is done after payment processing.

C. The transaction does not rollback on failure.

D. The payment gateway is too slow.

Solution

1. Step 1: Identify duplication cause

   If orders duplicate after retry, it means failed transactions were not properly rolled back.

2. Step 2: Understand rollback role

   Rollback prevents partial or repeated writes; missing rollback causes duplicates.

3. Final Answer:

   The transaction does not rollback on failure. -> Option C

4. Quick Check:

   Missing rollback causes duplicates = D [OK]

Hint: No rollback on failure causes duplicate orders [OK]

Common Mistakes:

• Blaming payment speed for duplicates
• Confusing order update timing with duplication
• Ignoring rollback importance

5. In an e-commerce system, why must transactional tests cover both payment and inventory updates together?

hard

A. To allow partial order processing for faster checkout.

B. To ensure that if payment succeeds but inventory update fails, the whole operation is reversed.

C. To separate payment and inventory logic for easier debugging.

D. To reduce database load by splitting transactions.

Solution

1. Step 1: Understand atomicity in transactions

   Atomicity means all parts succeed or all fail together to keep data consistent.

2. Step 2: Apply atomicity to payment and inventory

   If payment succeeds but inventory update fails, the transaction must rollback to avoid errors like charging without stock.

3. Final Answer:

   To ensure that if payment succeeds but inventory update fails, the whole operation is reversed. -> Option B

4. Quick Check:

   Atomic transaction covers payment and inventory = A [OK]

Hint: Test payment and inventory as one atomic operation [OK]

Common Mistakes:

• Allowing partial order processing
• Separating payment and inventory for speed
• Splitting transactions to reduce load