giovaniguizzo

8 ms·

1. 1.▲
   by giovaniguizzo 1y ago

   Interesting lib! Graphile Worker: PostgreSQL only Sidequest: Multiple backends (PostgreSQL, MySQL, SQLite, MongoDB) Graphile Worker: No built-in dashboard - you need external monitoring Sidequest: Comprehensive built-in web dashboard for jo
2. 2.▲
   by giovaniguizzo 1y ago

   Well, you don't need to worry. Sidequest only locks the rows it's gonna use, i.e., the job rows it manages. Any other data in your DB is not touched by Sidequest, so you should be safe :)
3. 3.▲
   by giovaniguizzo 1y ago

   Well, Sidequest comes with a comprehensive built-in dashboard that provides real-time monitoring, job management, and performance analytics, so there's that. You can probably deploy Sidequest a job processor for all your 20+ services.
4. 4.▲
   by giovaniguizzo 1y ago

   Nice to know SQLite will be useful. Just be mindful that SQLite does not work well in highly concurrent systems. So, if you have a single job runner process, it will work wonderfully. However, if you have many workers, then you might see a
5. 5.▲
   by giovaniguizzo 1y ago

   Hello! One of the creators of Sidequest here. Great question! Sidequest uses transaction-level row locks (`SELECT ... FOR UPDATE SKIP LOCKED`) when fetching jobs. This means each worker thread only locks the specific job rows it’s about to