Solutions for handling millions of timed (scheduled) messages?

Question

I'm evaluating possible solutions for handling a large quantity of queued messages, which must be delivered to workers at a certain date and time. The result of executing them is mostly updates to stored data, and they may or may not be originally triggered by user action.

For example, think of what you'd implement in a hypothetical large-scale StarCraft game server for storing and executing users' actions, like upgrading a building, hatching a soldier, all of which requires to be applied to the game state after several seconds or minutes after the player initiates them.

The problem is I can't seem to find the right term to name this problem area. There are several that looks similar, but different:

cron/task/job scheduler

• The content of the queue is not dynamic, it's predefined.
• Each task is scheduled.

message queue

• The content of the queue is dynamic.
• Each task is intended to be delivered immediately.

???

• The content of the queue is dynamic.
• Each task is scheduled.

If there are message queues that allow conditional delivery of messages, that might be it.

Summary:

1. What are these kind of technology called?
2. What are some of the solutions out there?

Answer 1

This just sounds like a trivial priority queue on the surface. The priority in this case is the time of completion, and you check the front of the queue to see when the next event is due. Pretty much every language comes with a priority queue or something that can easily be used as one, so I'm not sure what the actual problem is here.

Is it that you're worried about scalability, when it comes to millions of messages? Obviously 'millions' is a meaningless term - if that's millions per day, it's a trivial problem. If it's millions per second, then you can just scale horizontally, splitting the queue across multiple processes. (And the benefit of such a queue system is that this parallelization is really simple.)

I would bet that when implementing a large scale real-time strategy game server you would hit networking problems long before you start hitting problems with the message queue.

Answer 2

Have you tried looking at push queues by Iron.io? The content of the queue can be anything you like, and you specify a webhook to where the messages will be pushed to. You can also set a delay for each of the messages.

The webhook is static though for each queue and delay isn't always exactly on time (could be up to a minute off). If timing is more important or the ability of providing a different webhook per message is important, try looking at boomerang.io.

They say they are pretty accurate on the timing, you can provide a delay or unix timestamp for the webhook to return and that is per message. Sounds like either of those might work for you.