Alternatives to Azure Redis Cache logo

Alternatives to Azure Redis Cache

Amazon ElastiCache, Azure CDN, Redis, Hazelcast, and Aerospike are the most popular alternatives and competitors to Azure Redis Cache.
49
105
+ 1
3

What is Azure Redis Cache and what are its top alternatives?

It perfectly complements Azure database services such as Cosmos DB. It provides a cost-effective solution to scale read and write throughput of your data tier. Store and share database query results, session states, static contents, and more using a common cache-aside pattern.
Azure Redis Cache is a tool in the In-Memory Databases category of a tech stack.

Top Alternatives to Azure Redis Cache

  • Amazon ElastiCache
    Amazon ElastiCache

    ElastiCache improves the performance of web applications by allowing you to retrieve information from fast, managed, in-memory caches, instead of relying entirely on slower disk-based databases. ElastiCache supports Memcached and Redis. ...

  • Azure CDN
    Azure CDN

    It lets you reduce load times, save bandwidth, and speed responsiveness—whether you’re developing or managing websites or mobile apps, or encoding and distributing streaming media, gaming software, firmware updates, or IoT endpoints. ...

  • Redis
    Redis

    Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams. ...

  • Hazelcast
    Hazelcast

    With its various distributed data structures, distributed caching capabilities, elastic nature, memcache support, integration with Spring and Hibernate and more importantly with so many happy users, Hazelcast is feature-rich, enterprise-ready and developer-friendly in-memory data grid solution. ...

  • Aerospike
    Aerospike

    Aerospike is an open-source, modern database built from the ground up to push the limits of flash storage, processors and networks. It was designed to operate with predictable low latency at high throughput with uncompromising reliability – both high availability and ACID guarantees. ...

  • SAP HANA
    SAP HANA

    It is an application that uses in-memory database technology that allows the processing of massive amounts of real-time data in a short time. The in-memory computing engine allows it to process data stored in RAM as opposed to reading it from a disk. ...

  • MemSQL
    MemSQL

    MemSQL converges transactions and analytics for sub-second data processing and reporting. Real-time businesses can build robust applications on a simple and scalable infrastructure that complements and extends existing data pipelines. ...

  • Apache Ignite
    Apache Ignite

    It is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale ...

Azure Redis Cache alternatives & related posts

Amazon ElastiCache logo

Amazon ElastiCache

1.2K
918
149
Deploy, operate, and scale an in-memory cache in the cloud
1.2K
918
+ 1
149
PROS OF AMAZON ELASTICACHE
  • 57
    Redis
  • 32
    High-performance
  • 26
    Backed by amazon
  • 21
    Memcached
  • 13
    Elastic
CONS OF AMAZON ELASTICACHE
    Be the first to leave a con

    related Amazon ElastiCache posts

    John Kodumal

    As we've evolved or added additional infrastructure to our stack, we've biased towards managed services. Most new backing stores are Amazon RDS instances now. We do use self-managed PostgreSQL with TimescaleDB for time-series data—this is made HA with the use of Patroni and Consul.

    We also use managed Amazon ElastiCache instances instead of spinning up Amazon EC2 instances to run Redis workloads, as well as shifting to Amazon Kinesis instead of Kafka.

    See more
    Julien DeFrance
    Principal Software Engineer at Tophatter · | 16 upvotes · 2.5M views

    Back in 2014, I was given an opportunity to re-architect SmartZip Analytics platform, and flagship product: SmartTargeting. This is a SaaS software helping real estate professionals keeping up with their prospects and leads in a given neighborhood/territory, finding out (thanks to predictive analytics) who's the most likely to list/sell their home, and running cross-channel marketing automation against them: direct mail, online ads, email... The company also does provide Data APIs to Enterprise customers.

    I had inherited years and years of technical debt and I knew things had to change radically. The first enabler to this was to make use of the cloud and go with AWS, so we would stop re-inventing the wheel, and build around managed/scalable services.

    For the SaaS product, we kept on working with Rails as this was what my team had the most knowledge in. We've however broken up the monolith and decoupled the front-end application from the backend thanks to the use of Rails API so we'd get independently scalable micro-services from now on.

    Our various applications could now be deployed using AWS Elastic Beanstalk so we wouldn't waste any more efforts writing time-consuming Capistrano deployment scripts for instance. Combined with Docker so our application would run within its own container, independently from the underlying host configuration.

    Storage-wise, we went with Amazon S3 and ditched any pre-existing local or network storage people used to deal with in our legacy systems. On the database side: Amazon RDS / MySQL initially. Ultimately migrated to Amazon RDS for Aurora / MySQL when it got released. Once again, here you need a managed service your cloud provider handles for you.

    Future improvements / technology decisions included:

    Caching: Amazon ElastiCache / Memcached CDN: Amazon CloudFront Systems Integration: Segment / Zapier Data-warehousing: Amazon Redshift BI: Amazon Quicksight / Superset Search: Elasticsearch / Amazon Elasticsearch Service / Algolia Monitoring: New Relic

    As our usage grows, patterns changed, and/or our business needs evolved, my role as Engineering Manager then Director of Engineering was also to ensure my team kept on learning and innovating, while delivering on business value.

    One of these innovations was to get ourselves into Serverless : Adopting AWS Lambda was a big step forward. At the time, only available for Node.js (Not Ruby ) but a great way to handle cost efficiency, unpredictable traffic, sudden bursts of traffic... Ultimately you want the whole chain of services involved in a call to be serverless, and that's when we've started leveraging Amazon DynamoDB on these projects so they'd be fully scalable.

    See more
    Azure CDN logo

    Azure CDN

    53
    75
    1
    A global CDN solution for delivering high-bandwidth content
    53
    75
    + 1
    1
    PROS OF AZURE CDN
    • 1
      Low Latency
    CONS OF AZURE CDN
      Be the first to leave a con

      related Azure CDN posts

      Redis logo

      Redis

      47.2K
      36.3K
      3.9K
      Open source (BSD licensed), in-memory data structure store
      47.2K
      36.3K
      + 1
      3.9K
      PROS OF REDIS
      • 879
        Performance
      • 536
        Super fast
      • 511
        Ease of use
      • 441
        In-memory cache
      • 321
        Advanced key-value cache
      • 190
        Open source
      • 179
        Easy to deploy
      • 163
        Stable
      • 152
        Free
      • 120
        Fast
      • 40
        High-Performance
      • 39
        High Availability
      • 34
        Data Structures
      • 32
        Very Scalable
      • 23
        Replication
      • 20
        Great community
      • 19
        Pub/Sub
      • 17
        "NoSQL" key-value data store
      • 14
        Hashes
      • 12
        Sets
      • 10
        Sorted Sets
      • 9
        Lists
      • 8
        BSD licensed
      • 8
        NoSQL
      • 7
        Async replication
      • 7
        Integrates super easy with Sidekiq for Rails background
      • 7
        Bitmaps
      • 6
        Open Source
      • 6
        Keys with a limited time-to-live
      • 5
        Strings
      • 5
        Lua scripting
      • 4
        Awesomeness for Free!
      • 4
        Hyperloglogs
      • 3
        outstanding performance
      • 3
        Runs server side LUA
      • 3
        Networked
      • 3
        LRU eviction of keys
      • 3
        Written in ANSI C
      • 3
        Feature Rich
      • 3
        Transactions
      • 2
        Data structure server
      • 2
        Performance & ease of use
      • 1
        Existing Laravel Integration
      • 1
        Automatic failover
      • 1
        Easy to use
      • 1
        Object [key/value] size each 500 MB
      • 1
        Simple
      • 1
        Channels concept
      • 1
        Scalable
      • 1
        Temporarily kept on disk
      • 1
        Dont save data if no subscribers are found
      • 0
        Jk
      CONS OF REDIS
      • 14
        Cannot query objects directly
      • 2
        No secondary indexes for non-numeric data types
      • 1
        No WAL

      related Redis posts

      Robert Zuber

      We use MongoDB as our primary #datastore. Mongo's approach to replica sets enables some fantastic patterns for operations like maintenance, backups, and #ETL.

      As we pull #microservices from our #monolith, we are taking the opportunity to build them with their own datastores using PostgreSQL. We also use Redis to cache data we’d never store permanently, and to rate-limit our requests to partners’ APIs (like GitHub).

      When we’re dealing with large blobs of immutable data (logs, artifacts, and test results), we store them in Amazon S3. We handle any side-effects of S3’s eventual consistency model within our own code. This ensures that we deal with user requests correctly while writes are in process.

      See more

      I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

      We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

      Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis  for cache and other time sensitive operations.

      We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

      Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.

      See more
      Hazelcast logo

      Hazelcast

      263
      406
      56
      Clustering and highly scalable data distribution platform for Java
      263
      406
      + 1
      56
      PROS OF HAZELCAST
      • 10
        High Availibility
      • 6
        Distributed Locking
      • 5
        Distributed compute
      • 5
        Sharding
      • 4
        Load balancing
      • 3
        Sql query support in cluster wide
      • 3
        Map-reduce functionality
      • 3
        Written in java. runs on jvm
      • 3
        Publish-subscribe
      • 2
        Performance
      • 2
        Simple-to-use
      • 2
        Multiple client language support
      • 2
        Rest interface
      • 2
        Optimis locking for map
      • 1
        Super Fast
      • 1
        Admin Interface (Management Center)
      • 1
        Better Documentation
      • 1
        Easy to use
      CONS OF HAZELCAST
      • 3
        License needed for SSL

      related Hazelcast posts

      Aerospike logo

      Aerospike

      159
      228
      47
      Flash-optimized in-memory open source NoSQL database
      159
      228
      + 1
      47
      PROS OF AEROSPIKE
      • 15
        Ram and/or ssd persistence
      • 12
        Easy clustering support
      • 5
        Easy setup
      • 4
        Acid
      • 3
        Scale
      • 3
        Performance better than Redis
      • 3
        Petabyte Scale
      • 2
        Ease of use
      CONS OF AEROSPIKE
        Be the first to leave a con

        related Aerospike posts

        SAP HANA logo

        SAP HANA

        131
        106
        27
        An in-memory, column-oriented, relational database management system
        131
        106
        + 1
        27
        PROS OF SAP HANA
        • 5
          In-memory
        • 5
          SQL
        • 4
          Distributed
        • 4
          Performance
        • 2
          Realtime
        • 2
          Concurrent
        • 2
          OLAP
        • 2
          OLTP
        • 1
          JSON
        CONS OF SAP HANA
          Be the first to leave a con

          related SAP HANA posts

          Hi. We are planning to develop web, desktop, and mobile app for procurement, logistics, and contracts. Procure to Pay and Source to pay, spend management, supplier management, catalog management. ( similar to SAP Ariba, gap.com, coupa.com, ivalua.com vroozi.com, procurify.com

          We got stuck when deciding which technology stack is good for the future. We look forward to your kind guidance that will help us.

          We want to integrate with multiple databases with seamless bidirectional integration. What APIs and middleware available are best to achieve this? SAP HANA, Oracle, MySQL, MongoDB...

          ASP.NET / Node.js / Laravel. ......?

          Please guide us

          See more
          MemSQL logo

          MemSQL

          79
          160
          33
          Database for real-time transactions and analytics.
          79
          160
          + 1
          33
          PROS OF MEMSQL
          • 8
            Distributed
          • 4
            Realtime
          • 3
            JSON
          • 3
            Sql
          • 3
            Columnstore
          • 3
            Concurrent
          • 2
            Ultra fast
          • 2
            Scalable
          • 1
            Pipeline
          • 1
            Availability Group
          • 1
            S3
          • 1
            Mixed workload
          • 1
            Unlimited Storage Database
          CONS OF MEMSQL
            Be the first to leave a con

            related MemSQL posts

            Apache Ignite logo

            Apache Ignite

            78
            134
            29
            An open-source distributed database, caching and processing platform
            78
            134
            + 1
            29
            PROS OF APACHE IGNITE
            • 4
              Written in java. runs on jvm
            • 4
              Free
            • 3
              Load balancing
            • 3
              Multiple client language support
            • 3
              Sql query support in cluster wide
            • 3
              Rest interface
            • 3
              High Avaliability
            • 2
              Better Documentation
            • 2
              Easy to use
            • 1
              Distributed compute
            • 1
              Distributed Locking
            CONS OF APACHE IGNITE
              Be the first to leave a con

              related Apache Ignite posts