I am building a bubble app that communicates with another server (of my own design too). The server does some video processing that takes a while to complete and takes a bit of configuration to setup. It also is processing multiple videos simultaneously as independent tasks (ie different users requesting processing for different videos, etc), so each gets a unique job_id
I wanted to put together some sort of basic messaging system between my server and bubble. Rather than a more sophisticated message queue, I opted for a simple mysql table that lists jobs, their status, owner, etc.
When a video is processed there is a brief handshake, then the server does its thing. I want bubble to display some basic progress, errors, completion messages - which is all done by this messaging scheme.
I was going to use a recurring backend workflow to poll the mysql db, but I was thinking every 5 seconds and it seems that not what backend workflows are designed for. Right now I have it as a regular workflow (checking every 5 seconds) and everything works but it gunks up the browser.
I am rethinking my messaging approach. Suggestions?
