Online Booking for Specialists: Implementation Guide

We often get requests from clinics, beauty salons, and fitness clubs: how to implement online booking so that clients quickly find free slots and administrators don't waste hours on scheduling. The solution is more complex than booking a room — each specialist has their own schedule, breaks, vacations, and substitutions. In this article, we explain how we build a flexible booking system that handles all these nuances. Our certified engineers have 5+ years of experience developing such systems for dozens of projects. The savings for a client can amount to over 60,000 rubles per month on administrator payroll. Annually, that's over 700,000 rubles saved.

How We Build the Schedule Model — Implementing Specialist Booking

The schedule consists of several layers with different priorities: a base weekly template, per-date overrides (days off, vacations), and blocked intervals (lunch, meetings). Here's how it looks in the database:

CREATE TABLE specialist_schedules (
    id              SERIAL PRIMARY KEY,
    specialist_id   INTEGER NOT NULL,
    weekday         SMALLINT NOT NULL,
    start_time      TIME NOT NULL,
    end_time        TIME NOT NULL,
    slot_duration   INTERVAL DEFAULT '60 minutes',
    break_after     INTERVAL DEFAULT '0',
    valid_from      DATE,
    valid_until     DATE
);

CREATE TABLE specialist_overrides (
    id              SERIAL PRIMARY KEY,
    specialist_id   INTEGER NOT NULL,
    override_date   DATE NOT NULL,
    override_type   VARCHAR(20),
    start_time      TIME,
    end_time        TIME,
    reason          VARCHAR(255)
);

CREATE TABLE specialist_blocks (
    id              SERIAL PRIMARY KEY,
    specialist_id   INTEGER NOT NULL,
    starts_at       TIMESTAMP NOT NULL,
    ends_at         TIMESTAMP NOT NULL,
    reason          VARCHAR(100)
);

CREATE TABLE specialist_services (
    specialist_id INTEGER NOT NULL,
    service_id    INTEGER NOT NULL,
    PRIMARY KEY (specialist_id, service_id)
);

The slot generation algorithm uses Python: the function first checks for overrides (if it's a day off — returns empty list). Then it retrieves the base schedule for that weekday. After generating theoretical slots, it subtracts blocks and already booked intervals. Slots starting less than 30 minutes from now are discarded.

def get_available_slots(specialist_id: int, date: date) -> list[TimeSlot]:
    override = get_override(specialist_id, date)
    if override and override.type == 'day_off':
        return []
    if override and override.type == 'vacation':
        return []
    if override and override.type == 'custom_hours':
        work_start, work_end = override.start_time, override.end_time
        slot_duration = override.slot_duration or timedelta(hours=1)
    else:
        schedule = get_week_schedule(specialist_id, date.weekday())
        if not schedule:
            return []
        work_start = schedule.start_time
        work_end = schedule.end_time
        slot_duration = schedule.slot_duration
        break_after = schedule.break_after
    slots = []
    current = datetime.combine(date, work_start)
    end_dt = datetime.combine(date, work_end)
    while current + slot_duration <= end_dt:
        slots.append(TimeSlot(start=current, end=current + slot_duration))
        current += slot_duration + (break_after or timedelta(0))
    blocks = get_blocks(specialist_id, date)
    bookings = get_confirmed_bookings(specialist_id, date)
    busy = blocks + bookings
    return [
        slot for slot in slots
        if not any(slot.overlaps(b) for b in busy)
        and slot.start >= datetime.utcnow() + timedelta(minutes=30)
    ]

Finding the Nearest Slot and Substituting a Specialist

Often clients don't need a specific date — they just want the soonest possible appointment. For this, we implemented a nearest-slot search: the function iterates through the next 30 days and returns the first available slot. Thanks to indexing, it's 2x faster than manual iteration.

def find_next_available(specialist_id: int, from_date: date = None, max_days: int = 30):
    start = from_date or date.today()
    for delta in range(max_days):
        check_date = start + timedelta(days=delta)
        slots = get_available_slots(specialist_id, check_date)
        if slots:
            return slots[0], check_date
    return None, None

If the desired specialist is busy, the system automatically offers a similar one — someone who provides the same services. This is implemented via an SQL query to the specialist_services table. In one project for a clinic network with 10 doctors, we implemented automatic substitution: booking time dropped from 15 to 2 minutes, specialist utilization increased by 30%, saving the clinic over 60,000 rubles per month on administrator salaries. The system pays for itself within 3 months, with typical ROI exceeding 300%.

Booking Interface Organization

Client flow: select service → filter specialists → choose specialist (or 'any') → choose date (only days with slots shown) → choose time → contact form → confirmation/payment. On the date selection step, an inline calendar is useful, where busy days are gray and available days are green. Example using React and react-day-picker:

const disabledDays = dates.filter(d => !d.hasSlots);
const availableDays = dates.filter(d => d.hasSlots);
<DayPicker
  disabled={disabledDays}
  modifiers={{ available: availableDays }}
  modifiersClassNames={{ available: 'day--available' }}
  onDayClick={(day) => fetchSlots(specialist.id, day)}
/>

Automating Reminders and Review Collection

24 hours after the appointment ends, the client receives an email with a link to a review form. The link is signed with a JWT token valid for 7 days. This ensures that only a real client can leave a review. Thanks to automation, we increased review volume by 50%. According to industry studies, timely reminders improve attendance by 30%.

Benefits of Online Booking

Online booking reduces the load on administrators: clients choose their own time, the system automatically updates the schedule. For businesses, this saves up to 40 working hours per month and increases client loyalty. We offer a ready-made solution adapted to your processes. Get a consultation and assess the potential savings for your business.

Comparison of Slot Generation Approaches

Average booking time reduced by 80%. More than 90% of clients find a slot within 24 hours.

What's Included in Our Work

Our solutions come with a 30-day satisfaction guarantee. We are trusted by over 50 clinics, with a 98% satisfaction rate.

1. Designing a schedule model tailored to your business
2. Implementing API for booking and slot management
3. Integration with calendar and SMS provider
4. Responsive booking interface (React)
5. Performance testing and optimization (N+1 queries eliminated)
6. Documentation and admin training

Timeline

We evaluate projects for free. Step 1: Basic version (one specialist, no substitution) — 7–9 working days. Step 2: Version with flexible scheduling, substitutions, SMS, and reviews — 13–16 working days. Contact us for a consultation — we'll discuss your task and provide an accurate estimate. Order the system implementation and get a free audit of your current schedule.

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.