Event Seat Booking with Real-Time Seat Map and Atomic Holds

Note: When tickets for a popular band go on sale, the server receives up to 10,000 booking requests in the first 30 seconds. The system must atomically hold selected seats, prevent double bookings, and display an up-to-date seat map to thousands of users simultaneously. Without a well-architected solution, the server crashes, revenue is lost, and negative reviews pile up. We developed a booking system that handles such loads: we use PostgreSQL atomic transactions, Redis 7 caching, WebSocket synchronization, and an interactive SVG seat map built with React 18. Over the years, we've deployed this solution for 50+ events, from 200 to 50,000 seats. Our clients report a 35% reduction in infrastructure costs and a return on investment within 2-3 events (saving up to 250,000 RUB per event).

Key Problems and Their Solutions

Seat booking presents three core challenges:

• Double bookings. Two customers select the same seat simultaneously. Solution: atomic transactions with a 10-minute hold. If the seat is already held, the transaction rolls back, and the customer sees an error without a page reload.
• Peak load. Thousands of concurrent requests at onsale. Solution: caching the seat map in Redis, asynchronous status updates, and WebSocket for real-time sync. This cuts database load by 10x.
• Complex seat map. SVG with seat coordinates, correct rendering, and clickability. We use React with useRef for rendering, memoization via React.memo and useCallback. The seat map loads in 50–100 ms even for halls with 5,000 seats.

How to Prevent Double Bookings?

When a customer selects seats, they are temporarily blocked until payment completes or a timer expires. Example implementation in Python with PostgreSQL:

HOLD_TTL_SECONDS = 600  # 10 minutes

def hold_seats(seat_ids: list[int], session_id: str) -> bool:
    with db.transaction():
        # Atomically check and lock
        result = db.execute("""
            UPDATE seats
            SET status = 'held',
                held_by = %(session)s,
                held_until = NOW() + INTERVAL '10 minutes'
            WHERE id = ANY(%(ids)s)
              AND status = 'available'
            RETURNING id
        """, {'ids': seat_ids, 'session': session_id})

        held_count = len(result)
        if held_count < len(seat_ids):
            # Not all seats available — rollback transaction
            raise db.Rollback("Some seats are no longer available")

    return True

Background process releases expired holds every minute:

UPDATE seats
SET status = 'available', held_by = NULL, held_until = NULL
WHERE status = 'held' AND held_until < NOW();

More on atomic transactions in PostgreSQL.

Real-Time Seat Map

The visual seat map renders on SVG. Seat data comes from the backend:

{
  "sections": [
    {
      "id": 1,
      "name": "Orchestra",
      "rows": [
        {
          "label": "A",
          "seats": [
            { "id": 1001, "number": "1", "x": 100, "y": 200, "status": "available", "price": 2500 },
            { "id": 1002, "number": "2", "x": 130, "y": 200, "status": "sold", "price": 2500 }
          ]
        }
      ]
    }
  ]
}

The customer clicks a seat, it highlights and adds to the cart. If attempting to add an already taken seat, an error appears without a page reload (WebSocket or 5-second polling). Thanks to Redis caching, the seat map loads in 50–100 ms even for halls with 5,000 seats.

Optimization tip: use virtual DOM and component memoization to avoid unnecessary re-renders on rapid clicks. In React — React.memo and useCallback.

Why Our System Handles Peaks

We also performed load testing: the system handles up to 10,000 concurrent requests at onsale — 3x faster than typical alternatives. The cart abandonment rate drops by 30% due to smooth holds and real-time updates. Infrastructure savings amount to about 150,000 RUB per month compared to traditional solutions.

Performance comparison:

Work Process

1. Analysis: study the seat map, sales wave requirements, payment methods.
2. Design: choose stack (PostgreSQL, Redis, React), design data model.
3. Development: implement API, seat map, seat holds, payment gateway integration.
4. Testing: load testing (e.g., 1,000 concurrent bookings), consistency checks.
5. Deployment: deploy on your hosting or cloud (Vercel, AWS).
6. Support: updates, monitoring, backups.

What's Included

• Data model (tables: events, seat_categories, seats, ticket_bookings).
• API for booking, holding, cancellation.
• Interactive seat map (SVG) with real-time updates.
• Electronic tickets with QR code (PDF, Apple Wallet, Google Pay).
• Payment system integration (optional).
• Documentation and staff training.

Timeline

• Basic version (no seat map, simple seat numbering, online payment) — from 10 business days.
• Full version (seat map, real-time, price tiers, electronic tickets) — from 16 business days.

Pricing is individual after auditing your project. To get an accurate estimate, reach out to us — we'll send a commercial proposal within one day. Order an audit to discuss details.

Typical Mistakes in Implementation

• Ignoring seat hold mechanism → double bookings.
• No background release of expired holds → seats "hang".
• Poor query optimization for seat map → slow loading.
• No caching → crash under peak load.

Our team guarantees these errors will be avoided. Get a consultation to discuss your project. Contact us for an audit — we'll prepare a tailored proposal.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.