I'm looking for some guidance on deploying a Django application that needs to use multiple Celery workers. I've never worked with AWS before, so I'm trying to figure out whether to go with Elastic Container Service (ECS) or Elastic Beanstalk for this project.
Also, I'd love to know how to set up a development pipeline in AWS. On platforms like Railway, creating a 'staging' environment that mirrors production was straightforward. Can I do something similar on AWS? If so, how do I manage the database connections? Would the staging environment point to the same database as production? I'm eager to hear how experienced developers handle these setups.
2 Answers
I had a rough time with Beanstalk and Celery. It tried to simplify things but ended up complicating them instead. We faced so many obscure issues, and I really wish we’d transitioned from it sooner. Definitely think twice before going that route.
Hey, sorry to hear about your issues! If you have specific feedback, I'd love to hear it. You can reach out with suggestions through our feedback links.
I've used ECS with Fargate for all my web servers and workers, and it's been great! I initially deployed my first app with Beanstalk, but our DevOps team switched to ECS for production, and I see why. It's much more flexible and easier to manage than Beanstalk.
That sounds promising! What specifically made you prefer ECS over Beanstalk?
Were you using it with Redis or SQS?