Around 6 years ago, we started to improve our User Experience implementing new ways to process heavy tasks in a asyncronous way so our users wouldn't be affected waiting for an image to be processed or an email to be sent while visiting our sites. We could achieve that applying the Publish-subscribe messaging pattern, so all the heavy or none critical tasks could be executed in a different process improving not only the UX, also the server capacity and the load control. But some time afer we sucessfully build the system, a new requirement was thrown: we want to schedule the produced messages to be consumed later. Why later? Because some use cases require to schedule actions to be triggered in the future. So, as our infrastructure stack i ...