System Design: Designing an Online Auction System (eBay Scale)

System Design: Designing an Online Auction System

Mental Model

Connecting isolated components into a resilient, scalable, and observable distributed web.

Designing a high-scale auction system like eBay or a penny auction site is a classic concurrency challenge. The system must handle thousands of users bidding on the same item in the final seconds of an auction, ensuring that the highest bid is always recorded and no two bids are processed out of order.

1. Core Requirements

graph LR
    Producer[Producer Service] -->|Publish Event| Kafka[Kafka / Event Bus]
    Kafka -->|Consume| Consumer1[Consumer Group A]
    Kafka -->|Consume| Consumer2[Consumer Group B]
    Consumer1 --> DB1[(Primary DB)]
    Consumer2 --> Cache[(Redis)]

• Create Auction: Sellers can list items with a starting price and end time.
• Place Bid: Users can place a bid higher than the current price.
• Real-time Updates: All users must see the current highest bid immediately.
• Winning: Identifying the winner exactly at the end time.
• Scalability: Handling millions of auctions and high-frequency bidding surges.

2. The Bidding Challenge: Concurrency

The most critical part is the "Last Second Surge." If 10,000 people bid in the last 100ms, how do we decide who won?

Option A: Optimistic Locking (Database)

• Logic: UPDATE auctions SET current_price = ? WHERE id = ? AND current_price < ?.
• Pros: simple, keeps the database as the source of truth.
• Cons: High failure rate under heavy contention. Many users will see "Bid Failed" because someone else beat them by a microsecond.

Option B: Distributed Locking (Redis)

• Logic: Use a Redis-based lock per auction_id.
• Pros: Much faster than database locking.
• Cons: Complex to ensure durability. If Redis crashes, you could lose the final state of the bid.

3. High-Level Architecture

• Bid Service: Receives bids and validates them against the current price.
• Auction Service: Manages the lifecycle of auctions (Start/End).
• Notification Service: Pushes updates to bidders via WebSockets.
• Payment Service: Finalizes the transaction once an auction ends.

4. Real-time Updates: WebSocket Fan-out

When a new highest bid is accepted, every other person watching that auction needs to know instantly.

• The Process:
  1. Bid Service updates the database and Redis.
  2. It publishes an "Update" event to Apache Kafka.
  3. The WebSocket servers subscribe to Kafka and push the new price to all connected clients viewing that specific auction_id.

5. The "Auction End" Problem

How do you stop bids at exactly 12:00:00.000?

• Worker Workers: Use a distributed job scheduler (like our Job Scheduler article) to trigger an "Auction Closed" event at the exact timestamp.
• Buffer: The Bid Service should check the auction end time from a fast in-memory cache (Redis) before processing any bid to ensure no late bids are accepted.

6. Database Selection

• Metadata/Users:PostgreSQL.
• Bid History/Current State:PostgreSQL (for ACID) + Redis (for read-speed).
• Archival:Amazon S3 for finished auctions and historical bid logs.

Summary

Building an auction system is about Precision and Speed. By using Redis for high-frequency price updates and WebSockets for real-time fan-out, while maintaining a strict ACID-compliant source of truth in SQL, you can build a platform that handles the world's most intense bidding wars.

Engineering Standard: The "Staff" Perspective

In high-throughput distributed systems, the code we write is often the easiest part. The difficulty lies in how that code interacts with other components in the stack.

1. Data Integrity and The "P" in CAP

Whenever you are dealing with state (Databases, Caches, or In-memory stores), you must account for Network Partitions. In a standard Java microservice, we often choose Availability (AP) by using Eventual Consistency patterns. However, for financial ledgers, we must enforce Strong Consistency (CP), which usually involves distributed locks (Redis Redlock or Zookeeper) or a strictly linearizable sequence.

2. The Observability Pillar

Writing logic without observability is like flying a plane without a dashboard. Every production service must implement:

• Tracing (OpenTelemetry): Track a single request across 50 microservices.
• Metrics (Prometheus): Monitor Heap usage, Thread saturation, and P99 latencies.
• Structured Logging (ELK/Splunk): Never log raw strings; use JSON so you can query logs like a database.

3. Production Incident Prevention

To survive a 3:00 AM incident, we use:

• Circuit Breakers: Stop the bleeding if a downstream service is down.
• Bulkheads: Isolate thread pools so one failing endpoint doesn't crash the entire app.
• Retries with Exponential Backoff: Avoid the "Thundering Herd" problem when a service comes back online.

Critical Interview Nuance

When an interviewer asks you about this topic, don't just explain the code. Explain the Trade-offs. A Staff Engineer is someone who knows that every architectural decision is a choice between two "bad" outcomes. You are picking the one that aligns with the business goal.

Performance Checklist for High-Load Systems:

1. Minimize Object Creation: Use primitive arrays and reusable buffers.
2. Batching: Group 1,000 small writes into 1 large batch to save I/O cycles.
3. Async Processing: If the user doesn't need the result immediately, move it to a Message Queue (Kafka/SQS).

Advanced Architectural Blueprint: The Staff Perspective

In modern high-scale engineering, the primary differentiator between a Senior and a Staff Engineer is the ability to see beyond the local code and understand the Global System Impact. This section provides the exhaustive architectural context required to operate this component at a "MANG" (Meta, Amazon, Netflix, Google) scale.

1. High-Availability and Disaster Recovery (DR)

Every component in a production system must be designed for failure. If this component resides in a single availability zone, it is a liability.

• Multi-Region Active-Active: To achieve "Five Nines" (99.999%) availability, we replicate state across geographical regions using asynchronous replication or global consensus (Paxos/Raft).
• Chaos Engineering: We regularly inject "latency spikes" and "node kills" using tools like Chaos Mesh to ensure the system gracefully degrades without a total outage.

2. The Data Integrity Pillar (Consistency Models)

When managing state, we must choose our position on the CAP theorem spectrum.

3. Observability and "Day 2" Operations

Writing the code is only 10% of the lifecycle. The remaining 90% is spent monitoring and maintaining it.

• Tracing (OpenTelemetry): We use distributed tracing to map the request flow. This is critical when a P99 latency spike occurs in a mesh of 100+ microservices.
• Structured Logging: We avoid unstructured text. Every log line is a JSON object containing correlationId, tenantId, and latencyMs.
• Custom Metrics: We export business-level metrics (e.g., "Orders processed per second") to Prometheus to set up intelligent alerting with PagerDuty.

4. Production Readiness Checklist for Staff Engineers

• Capacity Planning: Have we performed load testing to find the "Breaking Point" of the service?
• Security Hardening: Is all communication encrypted using mTLS (Mutual TLS)?
• Backpressure Propagation: Does the service correctly return HTTP 429 or 503 when its internal thread pools are saturated?
• Idempotency: Can the same request be retried 10 times without side effects? (Critical for Payment systems).

Critical Interview Reflection

When an interviewer asks "How would you improve this?", they are looking for your ability to identify Bottlenecks. Focus on the network I/O, the database locking strategy, or the memory allocation patterns of the JVM. Explain the trade-offs between "Throughput" and "Latency." A Staff Engineer knows that you can never have both at their theoretical maximums.

Optimization Summary:

1. Reduce Context Switching: Use non-blocking I/O (Netty/Project Loom).
2. Minimize GC Pressure: Prefer primitive specialized collections over standard Generics.
3. Data Sharding: Use Consistent Hashing to avoid "Hot Shards."

Technical Trade-offs: Messaging Systems

Key Takeaways

• Create Auction: Sellers can list items with a starting price and end time.
• Place Bid: Users can place a bid higher than the current price.
• Real-time Updates: All users must see the current highest bid immediately.

Read Next

• System Design: Designing a Global Payment Gateway (Stripe Scale)
• System Design: Designing an Ad Click Aggregator
• System Design: Designing an Online Judge (LeetCode/HackerRank)

Verbal Interview Script

Interviewer: "How would you ensure high availability and fault tolerance for this specific architecture?"

Candidate: "To achieve 'Five Nines' (99.999%) availability, we must eliminate all Single Points of Failure (SPOF). I would deploy the API Gateway and stateless microservices across multiple Availability Zones (AZs) behind an active-active load balancer. For the data layer, I would use asynchronous replication to a read-replica in a different region for disaster recovery. Furthermore, it's not enough to just deploy redundantly; we must protect the system from cascading failures. I would implement strict timeouts, retry mechanisms with exponential backoff and jitter, and Circuit Breakers (using a library like Resilience4j) on all synchronous network calls between microservices."