Terraforming RabbitMQ on AWS for Celery
I’ve been making things with Django since around 2009. Usually I just deploy a thing onto a DigitalOcean droplet, and move on. For an interesting challenge this time around, I thought I’d make a thing that’s as AWS native as I possibly can, whilst keeping within the Free Tier. I wrote last week about the difficulties surrounding the fact that the AWS Free Tier doesn’t include Route53. This particular Django project has a ‘requirement’ that some of the processing of requests is actually queued, because it can be a bit on the time consuming side, potentially, so it’d make sense if that happens via a task queue....