Why e-commerce tests transactional design in HLD - Architecture Impact

System Overview - Why e-commerce tests transactional design

This system explains why e-commerce platforms test transactional design to ensure reliable order processing. Key requirements include maintaining data consistency, handling concurrent transactions, and preventing errors like double payments or lost orders.

Architecture Diagram

User
  |
  v
Load Balancer
  |
  v
API Gateway
  |
  v
Order Service <--> Payment Service
  |                 |
  v                 v
Database <---------> Cache
  |
  v
Message Queue
  |
  v
Notification Service

Components

User

client

Initiates order requests

Load Balancer

load_balancer

Distributes incoming requests evenly to API Gateway instances

API Gateway

api_gateway

Routes requests to appropriate backend services

Order Service

service

Handles order creation and transactional logic

Payment Service

service

Processes payments and ensures transactional integrity

Database

database

Stores order and payment data with ACID transactions

Cache

cache

Speeds up read operations and reduces database load

Message Queue

queue

Manages asynchronous tasks like notifications

Notification Service

service

Sends order confirmation and updates to users

Request Flow - 12 Hops

User → Load Balancer

Load Balancer → API Gateway

API Gateway → Order Service

Order Service → Cache

Order Service → Database

Order Service → Payment Service

Payment Service → Database

Payment Service → Order Service

Order Service → Database

Order Service → Message Queue

Message Queue → Notification Service

Notification Service → User

Failure Scenario

Component Fails:Database

Impact:Order and payment transactions fail; new orders cannot be saved; cache may serve stale data

Mitigation:Use database replication and failover; rely on cache for read-only operations; queue transactions for retry

Architecture Quiz - 3 Questions

Why does the Order Service check the Cache before the Database?

A To avoid using the API Gateway

B To reduce database load and speed up product availability checks

C To bypass payment processing

D To send notifications faster

Design Principle

This architecture demonstrates the importance of transactional design in e-commerce to maintain data consistency and reliability. Using database transactions ensures that order creation and payment processing succeed or fail together, preventing errors like double charges or lost orders. Caches improve performance but do not replace the need for strong transactional guarantees.

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