Overview
A zero-framework Node.js application exposes real-time floor status, a rolling 7-day slot calendar, patient self-booking with simulated payment, and a protected reception desk for walk-ins — all over a database layer that runs identically on local SQLite, Turso, or serverless PostgreSQL.
Problem & Context
Traditional appointment systems hide real-time doctor availability, funnel booking through phone queues, and split patient self-service from front-desk workflows — often on heavyweight stacks.
Key Capabilities
- Real-time doctor availability (available / busy / off-duty)
- Rolling 7-day slot booking with conflict auto-release
- Patient registration with scrypt password hashing and bearer sessions
- Reception desk for walk-in lookup and booking
- Tri-engine database abstraction (SQLite / Turso / PostgreSQL)
Engineering Notes
Tri-engine database abstraction
A unified layer translates SQLite ? placeholders to PostgreSQL $n, appends RETURNING id, and falls back to /tmp on read-only serverless filesystems — one codebase across three engines.
Zero-dependency framework architecture
A regex router over Node's native http module with no web framework, minimizing cold-start latency and dependency surface.
Slot state synchronization
Cancelling an appointment atomically returns its slot to the available pool, preventing double-booking.
Verified in the Repository
Facts below are verified in the project's source repository (static code audit). They are not runtime or business metrics.
- Live deployment verified on Vercel (truth-file audit, HIGH confidence)
- Multi-database layer supports PostgreSQL, Turso/LibSQL, and SQLite
- scrypt password hashing with per-user salts and bearer sessions
Current Status & Limitations
MVP · Live demo.
- Payment processing is simulated — not a PCI-compliant gateway.
- No automated test suite or CI pipeline.
- On serverless without an external database, SQLite falls back to /tmp and resets on cold start.