Beanstalk vs. Redis Software

For business or personal applications, where you wish your code to remain private and/or proprietary, Beanstalk could be a good fit. If you are also interested in beginning to automate with relative ease, their tools can be a great help. Code reviews can also be a key factor in the decision, as they provide a good framework for accountability.

Incentivized

Perfect solution for caching needs. If you have a bottleneck due to frequent data access to your database, then Redis can really help you by diverting those traffic away from your database. Its key/value pair structure also makes data lookup very efficient, providing excellent performance.

Incentivized

• Automation
• Code Review
• Support

Incentivized

• Easy for developers to understand. Unlike Riak, which I've used in the past, it's fast without having to worry about eventual consistency.
• Reliable. With a proper multi-node configuration, it can handle failover instantly.
• Configurable. We primarily still use Memcache for caching but one of the teams uses Redis for both long-term storage and temporary expiry keys without taking on another external dependency.
• Fast. We process tens of thousands of RPS and it doesn't skip a beat.

Incentivized

• Interface is not always intuitive, some areas are easier than others to navigate.
• Price plans are a little odd. However, they do seem to be flexible if a plan does not quite fit your needs.

Incentivized

• Redis is super fast but it comes with a cost. Whole dataset resides in RAM. So it can be costly as primary memory is more costly, then secondary ones.
• Persistence issues: To achieve it, Redis uses a memory dump to create a persistence snapshot, that's cool. But it requires some Linux Kernel tweaking to avoid performance degradation while the Redis server process is forking. This further causes latency.
• Master-slave structure side effect: Master-slave architecture comes with its own side effects. Please note that there will be only one master with multiple slaves for replication. All writing goes to the master, which creates more load on the master node. So, when the master goes down, the whole architecture does.

Incentivized

We will definitely continue using Redis because: 1. It is free and open source. 2. We already use it in so many applications, it will be hard for us to let go. 3. There isn't another competitive product that we know of that gives a better performance. 4. We never had any major issues with Redis, so no point turning our backs.

Incentivized

It is quite simple to set up for the purpose of managing user sessions in the backend. It can be easily integrated with other products or technologies, such as Spring in Java. If you need to actually display the data stored in Redis in your application this is a bit difficult to understand initially but is possible.

Incentivized

The support team has always been excellent in handling our mostly questions, rarely problems. They are responsive, find the solution and get us moving forward again. I have never had to escalate a case with them. They have always solved our problems in a very timely manner. I highly commend the support team.

Incentivized

Whitelisting of the AWS lambda functions.

Incentivized

If you are creating open source applications, there is almost no reason not to use GitHub. If you do need private repositories (for proprietary or private, business or personal use), Bitbucket could be an excellent solution. Beanstalk's main advantages lie in the support (which is excellent), deployment tools, and code review features.

Incentivized

UI isn't that great compared to the other competitors. The management of our memcached cluster was becoming pretty complicated as the application grew in size. Redis is a much better option compared to memcached. Redis is bit unreliable compared to the alternative RabbitMQ especially when it needs to be integrated with Celery.

Incentivized

• Increased automation => better accuracy and efficiency of maintenance/launches
• Better insights into ongoing work and past modifications to code => lower chance of error and more efficient troubleshooting

Incentivized

• Existing tools like Redisson that were built over Redis reduced dev time in solving challenging problems, which had a positive impact on ROI.
• We initially misused Redis for persistent storage which had a negative impact on ROI because we were paying a lot for inactive users.
• The increased performance we achieved using Redis in areas like locking helped us improve the performance of our system reducing the likelihood of system timeouts.

Incentivized