Currently, we request the flight combinations on every visit to the page. Due to the high amount of combinations to query, it takes a long time which is really bad UX.
The goal of this issue is to find a way to persist the flight information (e.g. KV db, a simple file version controlled, an SQLite, etc.) and a mechanism to regularly keep it up to date (e.g. a cronjob calling a protected endpoint, a GitHub Action, etc.)
It might be handy to explore a simple way that just works ™️ even if it's not the optimal way, and iterate over it later.
Currently, we request the flight combinations on every visit to the page. Due to the high amount of combinations to query, it takes a long time which is really bad UX.
The goal of this issue is to find a way to persist the flight information (e.g. KV db, a simple file version controlled, an SQLite, etc.) and a mechanism to regularly keep it up to date (e.g. a cronjob calling a protected endpoint, a GitHub Action, etc.)
It might be handy to explore a simple way that just works ™️ even if it's not the optimal way, and iterate over it later.