147 karma · joined March 10, 2016
It doesn't matter what you and your small group of friends think about the app. People will react to your app differently. So, PREPARE. TO. WEBSCALE!
- More people get vaccinated: A
- Less people remain unvaccinated: A' (=1-A)
- More people get infected: B
B/A' will of course grow more rapidly than B/A
*##span,a,div,p,li:style(color: #000000 !important; background: #fff !important;)First, you'll learn about ack/noack and get the worker ack on success.
Then, you'll learn about dead letter queue ... etc for delayed retries.
Now, you'll have a topic exchange and a bit hairy routing in place using wildcards.
And you mistakenly set dead letter routing key so that expired messages end up in multiple queues (retry queues and actual worker queue ... ).
Then you rewrite your service in python and use Celery or something.
It's nearly impossible to get RabbitMQ working correctly within few months.
And I forgot about HA. Paying for hosted RabbitMQ might be better. But CloudAMQP in particular could be tricky as well. It can run out of AWS IOPS and your production gets hosed.
Also setting up monitoring on queue health, shoveling error queues ... etc take time to learn and apply. Be careful about routing keys when you shovel error queue to a topic.