What abstraction to use for Producer - consumer model with queue implementation

Have you looked at Oban?

Or Broadway?

That’s an interesting problem statement. At first reading it seems like it might be good to model this with processes (using either GenServer or Agent). Can you explain more why you need to persist the operators state in the database? Could that instead be stored entirely in memory?

Based on my understanding of your description, OPQ doesn’t seem like a good fit because it simply has generic worker processes, whereas you need to assign users from the queue to a specific available operator.

I think what you primarily need is a FIFO queue of users, then whenever an operator becomes available, it can request the next user from the queue. That way the operators don’t need to talk to each other, instead they just need to pull items off of the shared queue. Depending on your scaling needs a single GenServer holding the queue of users should work fine (Look at the erlang queue module).

It’s not really a producer consumer problem, I think it’s more related to limited resource access (where operators are those limited resources)… In which case I would look for design like poolboy, with checkin/checkout.

There is Erlang :queue module to manage queue.

If You want to be fast, You shouldn’t think in terms of database. As mentionned by @axelson there are many ways to go faster than db. At most, I would use db to load state for a GenServer. When I really need speed, I reach for ETS.

I don’t think GenStage is a good fit, it’s more like a pipeline, with successive steps.

It looks like a call center model, or a helpdesk service.

There are similar ideas in voip asterisk server Asterisk Agents - VoIP-Info

Thanks for the reply! Actually our business requires us to store various states in the Database because those will be used for deciding the billing and also analytics (I know for analytics we can use other approaches). The number of users can go upto 5000 at peak.

Thank you! Looking into ETS

Oban too has generic workers which won’t fit in my use case.

Whenever an operator’s state is ‘available’, I need to allocate the first member of the user queue to this operator and pop him out of the queue.

Operator sounds like a Rabbitmq consumer that can only handle 1 task at a time, and user queue is Rabbitmq messages queued up under a certain topic (channel). This is more of a routing problem than consumer/producer problem. I don’t have any concrete implementation I can suggest but rabbitmq is open source so you could look at their code