0

In my app I let users send messages and emails. I'd like to enable them to schedule them for sending - i.e. set a time and date when they'll be sent.

I've got quite a lot of messages being sent - how best can I architect this so that it'll scale? I've got them being stored in PostgreSQL for now, but I have no way other than polling to check which need to be sent. I'd like to avoid polling if possible.

I'm currently running PHP, node.js, redis, PostgreSQL and RabbitMQ on EC2, so any combination of those is favourable.

4

1 回答 1

1

如果您只使用数据库，您将轮询发送消息，但由于您有 RabbitMQ，您可以设置延迟消息。

我找到了这篇关于这个话题的文章。

于 2013-03-08T16:08:01.743 回答