67726e / meteor.jobs Goto Github PK

We should publish types to the @types project for public consumption to ease developer burden.

We should codify the 1 vs. N server workflow more explicitly than setServerId - This would allow for instant startup in the case of a single server, probably the most common workflow. This could dovetail nicely with efforts to use a strategy pattern to allow a fine-grained approach to splitting work across N servers. This could allow a specific server to handle a specific job type, or N servers to handle N job types.

The current job execution strategy is a round-robin approach, picking the most recent "due" job followed by the most recent "due" job of a different type and on and on and on... we should codify this as a plug-and-play strategy and allow for alternative queueing algorithms.