comblia.

RELIABILITY

How Comblia prevents double booking

We would rather show what is verified, and what is not yet.

The guarantees

  1. One operation decides. Checking that the slot is free and saving the booking happen in a single operation in the database. Two people cannot both get through.
  2. Partial overlaps included. An appointment from 1:15 p.m. to 2:15 p.m. is refused if 1 p.m. to 2 p.m. already exists, for the provider as well as for the room, buffer included.
  3. A refused move loses nothing. If the new slot is taken, the appointment stays exactly where it was.
  4. A retry does not create a duplicate. Each request carries a key: if the network drops and the request is sent again, only one appointment exists.
  5. Everything stays consistent. Appointments, waitlist and log are updated together. If one part fails, nothing is saved halfway.
  6. Separate businesses. Each business sees only its own data, and each employee has individual access that can be revoked immediately.
  7. Clock changes. The repeated hour in the fall is offered twice, with its offset, and the skipped hour in the spring is never offered.

What has been tested

All of these checks use fictional data.

What works today

What is still to be proven