adewes
commented
2 years ago We can add caching to the getAppointmentsByZipCode endpoint, either on the level of the API or in the load balancer. In general, precomputed appointments by zip code can be stored in Redis and e.g. only recomputed every 10 seconds, which would dramatically reduce the load on the database as that endpoint is the most widely used one.
Currently the API fetches relevant appointments for users with a rather naive search process. We should improve this to make the system ready to process a larger number of advertised appointments (10.000-100.000).