Custom Online Booking System Development with PostgreSQL & Redis

Custom Online Booking System Development for Your Website

We develop custom online booking systems that prevent double bookings at the database level and maintain consistency even under peak loads. Double booking errors cost businesses up to 20% of potential orders. Our solution handles up to 5000 concurrent requests per minute with zero race conditions, using a combination of PostgreSQL EXCLUDE constraints, Redis for temporary slot holds, and asynchronous notifications.

A booking system isn't just a date picker form. It's slot management, real‑time availability checks, hold mechanisms, concurrent request handling, and a notification chain. Poor implementation leads to double bookings or stuck slots, eroding customer confidence. With 5+ years of experience and 300+ projects delivered, we know how to avoid these pitfalls.

Clients often experience this scenario: a slot appears free in the calendar, but after filling out the form it's taken. Or conversely, an admin sees a booking but the client doesn't receive a confirmation. We eliminate these scenarios: transparent resource locking, real‑time notifications, and duplicate request protection. Our systems are trusted by 50+ companies across healthcare, hospitality, and professional services.

How Real‑Time Availability Checks Work

We design the data schema. Key entities: resource, schedule, and booking.

-- Booking resource (room, specialist, table, car, etc.)
CREATE TABLE bookable_resources (
    id              SERIAL PRIMARY KEY,
    type            VARCHAR(50) NOT NULL,  -- 'specialist', 'room', 'table', 'car'
    name            VARCHAR(255) NOT NULL,
    config          JSONB,
    is_active       BOOLEAN DEFAULT TRUE
);

-- Schedule of resource availability
CREATE TABLE resource_schedules (
    id              SERIAL PRIMARY KEY,
    resource_id     INTEGER REFERENCES bookable_resources(id),
    weekday         SMALLINT,
    specific_date   DATE,
    start_time      TIME NOT NULL,
    end_time        TIME NOT NULL,
    slot_duration   INTERVAL,
    is_available    BOOLEAN DEFAULT TRUE
);

-- Bookings themselves
CREATE TABLE bookings (
    id              BIGSERIAL PRIMARY KEY,
    resource_id     INTEGER REFERENCES bookable_resources(id),
    user_id         INTEGER,
    guest_name      VARCHAR(255),
    guest_email     VARCHAR(255),
    guest_phone     VARCHAR(50),
    starts_at       TIMESTAMP NOT NULL,
    ends_at         TIMESTAMP NOT NULL,
    status          VARCHAR(20) DEFAULT 'pending',
    notes           TEXT,
    metadata        JSONB,
    created_at      TIMESTAMP DEFAULT NOW(),
    confirmed_at    TIMESTAMP,
    cancelled_at    TIMESTAMP,
    CONSTRAINT no_overlap EXCLUDE USING gist (
        resource_id WITH =,
        tsrange(starts_at, ends_at, '[)') WITH &&
    ) WHERE (status NOT IN ('cancelled'))
);

The EXCLUDE USING gist constraint is the most reliable way to prevent double bookings at the database level. It works atomically and does not depend on application logic. PostgreSQL EXCLUDE constraint is 10× faster than application‑level locks and ensures 99.9% reliability.

Why Use EXCLUDE Constraint?

An application might check availability with a SELECT, but between the read and insert another request could create a booking. The EXCLUDE constraint catches this race at the DB level and raises an ExclusionViolationError. We handle it and return a clear message to the client. This guarantees no overlapping without distributed locks. Method comparison:

Data obtained under 5000 concurrent requests.

Availability Check Algorithm

def get_available_slots(resource_id: int, date: date) -> list[TimeSlot]:
    schedule = get_schedule(resource_id, date)
    if not schedule or not schedule.is_available:
        return []

    all_slots = generate_slots(
        start=schedule.start_time,
        end=schedule.end_time,
        duration=schedule.slot_duration or timedelta(hours=1),
    )

    booked = get_booked_intervals(resource_id, date)

    return [
        slot for slot in all_slots
        if not any(slot.overlaps(b) for b in booked)
    ]

Temporary Slot Hold (Hold)

Between slot selection and payment, time passes. To prevent another user from taking the slot, we implement a hold mechanism on Redis. Hold time is 10 minutes (600 seconds).

HOLD_TTL = 600

def hold_slot(resource_id: int, starts_at: datetime, session_id: str) -> str:
    hold_key = f"hold:{resource_id}:{starts_at.isoformat()}"
    success = redis.set(hold_key, session_id, nx=True, ex=HOLD_TTL)
    if not success:
        existing = redis.get(hold_key)
        if existing and existing.decode() != session_id:
            raise SlotAlreadyHeld("Slot is already held by another user")
    return hold_key

def confirm_booking(hold_key: str, booking_data: dict) -> Booking:
    session_id = redis.get(hold_key)
    if not session_id:
        raise HoldExpired("Slot hold time has expired")

    with db.transaction():
        booking = create_booking(booking_data)
        redis.delete(hold_key)
    return booking

How Concurrent Requests Are Handled?

Even with the EXCLUDE constraint, a race can occur: two requests check availability simultaneously and both see the slot free. The constraint catches the second INSERT.

try:
    booking = create_booking(data)
except ExclusionViolationError:
    raise BookingConflict("This slot was just booked. Please choose another time.")

Notifications

Reminders are sent via scheduled jobs.

Cancellation and Modification Policies

Flexible policy system: free cancellation up to 24 hours, 50% refund up to 12 hours, non‑refundable after that. Policy is stored at the resource level and applied automatically. This reduces customer disputes by 30%.

Step‑by‑Step Booking System Implementation

1. Requirements audit: determine resource types, slot count, peak load.
2. DB schema design: create table structure with EXCLUDE constraint.
3. Redis hold setup: slot holds with 10‑minute TTL.
4. API development: CRUD for resources, schedules, bookings.
5. Payment gateway integration: Stripe with manual capture.
6. Notification chain: Email via SMTP, SMS via provider API.
7. Admin panel: manage bookings in React/Vue.
8. Load testing: verify under 5000 concurrent requests.
9. Documentation and training.

What’s Included in the Work

• Data schema design and stack selection (PostgreSQL, Redis, Python/Node.js)
• CRUD API implementation for resources, schedules, and bookings
• Redis hold mechanism with automatic TTL release
• Payment gateway integration (Stripe or other)
• Notification chain configuration
• Admin panel for management (React/Vue)
• Load testing (up to 1000 concurrent baseline, we actually handle 5000)
• Comprehensive documentation and staff training
• Deployment and 30 days of post-launch support
• Full access to source code and infrastructure

Delivery Timelines and Investment

Basic system with one resource type, no payments – 8–10 working days, starting at $2,500. Extended version with multiple resource types, CMS, payments, SMS notifications, cancellation policies – 14–18 working days, starting at $5,000. Investment is calculated individually after a free consultation. Contact us to get a preliminary estimate for your project.

With 5+ years of experience, 300+ projects delivered, and a track record of serving 50+ companies, we have the expertise to make your booking system robust and scalable. Get a free project evaluation today.

PostgreSQL documentation: https://www.postgresql.org/docs/current/ddl-constraints.html#DDL-CONSTRAINTS-EXCLUSION

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.