River: A fast, robust job queue for Go and Postgres

Re:River: A fast, robust job queue for Go and Postgres by justinclift on Monday November 20, 2023 @11:45PM (#38359374)

Does it do job completion notification?

Along the lines of:

    _, err := river.Execute(context.Background(), j) // Enqueue the job, and wait for completion
    if err != nil {
        log.Fatalf("Unable to execute job: %s", err)
    }
    log.Printf("Job completed")

Does that make sense?

[ Parent | on HN ]

Re:River: A fast, robust job queue for Go and Postgres by bgentry on Tuesday November 21, 2023 @10:45AM (#38365203)

It sounds like you're looking to be able to find out when a job has finished working, no matter which node it was run on. No, River does not have a mechanism for that today. It's definitely something we've talked about though.

[ Parent | on HN ]

Re:River: A fast, robust job queue for Go and Postgres by justinclift on Tuesday November 21, 2023 @12:25PM (#38366824)

Thanks. Yeah, that's definitely a requirement of the queueing systems I'm working with.

It's effectively "run this remote function, and return when you have the result data".

Fan-out RPC (-ish) style stuff, rather than async "queue an email for sending later".

[ Parent | on HN ]