---
title: "Discussion on \"Why I Compute Every Appointment Slot from Scratch on Every Request\" | Hashnode"
description: "Discussion on \"Why I Compute Every Appointment Slot from Scratch on Every Request\". The obvious approach to appointment scheduling is a lookup table. Run a job at midnight. Generate every possible slot for the next two…"
url: "https://hashnode.com/posts/clinical-scheduling-engine-real-time-slot-computation/69e391ccb62bf7a492241ae8"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Why I Compute Every Appointment Slot from Scratch on Every Request](https://kingsleyonoh.hashnode.dev/clinical-scheduling-engine-real-time-slot-computation?utm_source=hashnode&utm_medium=feed)

The obvious approach to appointment scheduling is a lookup table. Run a job at midnight. Generate every possible slot for the next two…

Apr 18 · 7 min read · kingsleyonoh.hashnode.dev  
Read the article

-   [#constraint-solving](https://hashnode.com/tag/constraint-solving)
-   [#scoring-algorithms](https://hashnode.com/tag/scoring-algorithms)
-   [#postgresql](https://hashnode.com/tag/postgresql)
-   [#scheduling](https://hashnode.com/tag/scheduling)

## Written by

[kingsley ebube onoh](https://hashnode.com/@kingsley-onoh)

@kingsley-onoh · Lagos, Nigeria

  
[View profile](https://hashnode.com/@kingsley-onoh)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
