[FR]: Job ordering #380

Activity

1. brandur commented on Jun 3, 2024

   

   brandur

   on Jun 3, 2024

   Contributor

   More actions

   This does seem like something that might be useful in the project — I've seen the same kind of thing elsewhere too.

   I'm not sure we're likely to get to this right away, so I'd suggest this workaround in the meantime: using the SMS example again, instead of putting the SMS messages directly in a River job, hold them instead as a separate database model that's ordered naturally on insert order. Then, your River job runs and just clears whatever SMS messages it finds in the database:

   func (w *SendSMSWorker) Work(ctx context.Context, job *river.Job[SendSMSArgs]) error {
       ...
   
       messagesToSend, err := queries.SMSMessageLoadByUser(job.UserID)
       ...
   
       for _, message := range messagesToSend {
           // send SMS message
       }
   
       return nil
   }
2. bgentry

   added

   enhancementNew feature or requestNew feature or request

   on Jul 7, 2024
3. riverqueue

   locked and limited conversation to collaborators on Jul 7, 2024
4. bgentry

   converted this issue into a discussion #431 on Jul 7, 2024