Craig DesBrisay

Joined

260 Experience
2 Lessons Completed
0 Questions Solved

Activity

Posted in Redis on Digital Ocean vs. AWS/ElastiCache

Thanks, Chris. This is what I suspected. Redis on the same machine seems like a good easy solution. And although it would be a nice problem to need to process hundreds of thousands of jobs, realistically I'll never need that.

Posted in Redis on Digital Ocean vs. AWS/ElastiCache

I'm running a Rails app on AWS Elastic Beanstalk / EC2 which also uses ElastiCache / Redis to run background jobs with Sidekiq. If I'm not mistaken, ElastiCache is a completely separate service than the core EC2 compute engine, so any Redis storage or I/O activity shouldn't impact the EC2 compute instance performance or storage requirements, other than of course the jobs themselves being executed on EC2.

How does this work on Digital Ocean? I've setup a droplet with the identical Rails application along with Redis. However, it seems like the Redis database is on the same droplet as the compute engine on digital ocean. If for some reason there should happen to be a large number of jobs queued in a short period of time, will the Redis activity negatively impact the performance of the droplet since it doesn't seem to be extracted to its own service like it is with ElastiCache on AWS?

By the way, the Hatch service from GoRails makes it super easy to deploy an app to Digital Ocean. Definitely recommend it for anyone who isn't a seasoned DevOps engineer or Linux guru. I have no idea what I'm doing with Linux and I was able to deploy my app to digital ocean with very little pain / effort.

Screencast tutorials to help you learn Ruby on Rails, Javascript, Hotwire, Turbo, Stimulus.js, PostgreSQL, MySQL, Ubuntu, and more.

© 2024 GoRails, LLC. All rights reserved.