Akamai CDN vs. Redis Software

Akamai is a well-established brand name with a great product. It meets and many time exceeds the needs for global content delivery and security management layer at the edge. Fine grain security tuning seems cumbersome as the definition of the app keeps changing. It also requires an investment of time for the setup which doesn't necessarily make sense for smaller scale scenarios. Some products offered by AWS, Azure or the Google Cloud can be more tightly integrated with cloud provider offerings thus easier to configure.

Incentivized

Redis has been a great investment for our organization as we needed a solution for high speed data caching. The ramp up and integration was quite easy. Redis handles automatic failover internally, so no crashes provides high availability. On the fly scaling scale to more/less cores and memory as and when needed.

Incentivized

• Content offloading - once rules are set up within Akamai you don't need to even think about how many images or large JavaScript or CSS files (for example) are being served from your own estate, Akamai takes care of it all via rules that are quick, easy and flexible.
• Page caching - for pages that don't change very often Akamai allows you to set up rules, quickly and easily, to serve up your page content for you, which takes even more load away from your origin servers.
• Quick rollback - the Akamai system allows easy testing of rules and changes via a staging system, and also offers a quick rollback option, which is perfect for the rare occasions when something has been set up incorrectly.

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

• The interface in their control centre could be a bit more user-friendly with some of the settings in places that you wouldn't expect them to be. The search offsets this problem to an extent but it's still sometimes slower than you'd like to find what you are looking for.

Incentivized

• We had some difficulty scaling Redis without it becoming prohibitively expensive.
• Redis has very simple search capabilities, which means its not suitable for all use cases.
• Redis doesn't have good native support for storing data in object form and many libraries built over it return data as a string, meaning you need build your own serialization layer over it.

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

Their support documents are excellent and provide a lot of useful information for all their services. The only reason I didn't give them a 10 is that the time it takes for them to respond to an issue could be slightly faster.

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

We've used -- and considered -- a whole number of CDN offerings. The good news is that almost all of the CDN products on the market are terrific, and will pay for themselves via increased customer satisfaction and lower monthly hosting bills. For some cases, we're still more likely to suggest CloudFlare (which has a free tier) or an integrated offering from a cloud provider, like Cloudfront.

Incentivized

We are big users of MySQL and PostgreSQL. We were looking at replacing our aging web page caching technology and found that we could do it in SQL, but there was a NoSQL movement happening at the time. We dabbled a bit in the NoSQL scene just to get an idea of what it was about and whether it was for us. We tried a bunch, but I can only seem to remember Mongo and Couch. Mongo had big issues early on that drove us to Redis and we couldn't quite figure out how to deploy couch.

Incentivized

• Akamai RoI improved over a period of times since it comes with heavy costs, however global deliveries in over 100 counties and global web platforms usage helps improve RoI
• With the complex UI challenges, ROI could be impacted negatively when you have to invest in operations and time.

Incentivized

• Redis has helped us increase our throughput and server data to a growing amount of traffic while keeping our app fast. We couldn't have grown without the ability to easily cache data that Redis provides.
• Redis has helped us decrease the load on our database. By being able to scale up and cache important data, we reduce the load on our database reducing costs and infra issues.
• Running a Redis node on something like AWS can be costly, but it is often a requirement for scaling a company. If you need data quickly and your business is already a positive ROI, Redis is worth the investment.

Incentivized