Open maxrohleder opened 4 years ago
I am unsure as to what you mean by local storage. Local storage is implemented on the client side, by the browser. Do you mean something like a session cache? We then could either build our own or use something like redis.
Sorry for the term local storage. I meant to store the queue only temporarily as a variable in the servers process memory. The positions change every couple of minutes and with the current implementation all changes are propagated into the db. There is no long-term storage needed for the queue.
One problem could be multiple instances of the backend service because google implements load balancing. Would have to put them onto a shared memory or something..
Does the queue need to be stored on database or can it be handled by backend local storage?
--> Reduce the number of database read/writes drastically.