I'm mostly a typescript developer but I'm learning Go for a backend api project I've been working on (node's pain points started showing up a lot lately). The api needs a *persistent* backend queue. If the worker or api goes down I want the jobs to be stored on disk so the worker and pick up where it left off and continue with the queue. Also, some of these jobs might be somewhat cpu intensive (non-LLM natural language processing mostly). What are my options for this in Go? In node I used bullmq but tbh didn't love it. River seems interesting but I worried it would slam my database on the queue and on the api at the same time (also so many features being locked behind pro is kinda :/). submitted by /u/roboticfoxdeer [link] [comments]