Alternatives to Memcached logo

Alternatives to Memcached

Redis, Ehcache, Varnish, Hazelcast, and MongoDB are the most popular alternatives and competitors to Memcached.
5.1K
3.5K
+ 1
465

What is Memcached and what are its top alternatives?

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.
Memcached is a tool in the Databases category of a tech stack.
Memcached is an open source tool with 10.8K GitHub stars and 2.9K GitHub forks. Here’s a link to Memcached's open source repository on GitHub

Top Alternatives to Memcached

  • Redis

    Redis

    Redis is an open source, BSD licensed, advanced key-value store. It is often referred to as a data structure server since keys can contain strings, hashes, lists, sets and sorted sets. ...

  • Ehcache

    Ehcache

    Ehcache is an open source, standards-based cache for boosting performance, offloading your database, and simplifying scalability. It's the most widely-used Java-based cache because it's robust, proven, and full-featured. Ehcache scales from in-process, with one or more nodes, all the way to mixed in-process/out-of-process configurations with terabyte-sized caches. ...

  • Varnish

    Varnish

    Varnish Cache is a web application accelerator also known as a caching HTTP reverse proxy. You install it in front of any server that speaks HTTP and configure it to cache the contents. Varnish Cache is really, really fast. It typically speeds up delivery with a factor of 300 - 1000x, depending on your architecture. ...

  • 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. ...

  • MongoDB

    MongoDB

    MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding. ...

  • Couchbase

    Couchbase

    Developed as an alternative to traditionally inflexible SQL databases, the Couchbase NoSQL database is built on an open source foundation and architected to help developers solve real-world problems and meet high scalability demands. ...

  • Memcached Cloud

    Memcached Cloud

    Memcached Cloud is a fully-managed service for running your Memcached in a reliable and fail-safe manner. Your dataset is constantly replicated, so if a node fails, an auto-switchover mechanism guarantees data is served without interruption. Memcached Cloud provides various data persistence options as well as remote backups for disaster recovery purposes. ...

  • etcd

    etcd

    etcd is a distributed key value store that provides a reliable way to store data across a cluster of machines. It’s open-source and available on GitHub. etcd gracefully handles master elections during network partitions and will tolerate machine failure, including the master. ...

Memcached alternatives & related posts

Redis logo

Redis

35.2K
25.5K
3.9K
An in-memory database that persists on disk
35.2K
25.5K
+ 1
3.9K
PROS OF REDIS
  • 875
    Performance
  • 535
    Super fast
  • 510
    Ease of use
  • 442
    In-memory cache
  • 321
    Advanced key-value cache
  • 189
    Open source
  • 179
    Easy to deploy
  • 163
    Stable
  • 152
    Free
  • 120
    Fast
  • 39
    High-Performance
  • 38
    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
  • 11
    Cannot query objects directly
  • 1
    No WAL
  • 1
    No secondary indexes for non-numeric data types

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
Ehcache logo

Ehcache

65
110
4
Java's Most Widely-Used Cache
65
110
+ 1
4
PROS OF EHCACHE
  • 1
    Way Faster than Redis and Elasticache Redis
  • 1
    Easy setup
  • 1
    Simpler to run in testing environment
  • 1
    Container doesn't have to be running for local tests
CONS OF EHCACHE
    Be the first to leave a con

    related Ehcache posts

    Varnish logo

    Varnish

    11K
    1.6K
    358
    High-performance HTTP accelerator
    11K
    1.6K
    + 1
    358
    PROS OF VARNISH
    • 102
      High-performance
    • 66
      Very Fast
    • 56
      Very Stable
    • 43
      Very Robust
    • 36
      HTTP reverse proxy
    • 20
      Open Source
    • 17
      Web application accelerator
    • 10
      Easy to config
    • 4
      Widely Used
    • 3
      Great community
    • 1
      Essential software for HTTP
    CONS OF VARNISH
      Be the first to leave a con

      related Varnish posts

      Tom Klein

      We're using Git through GitHub for public repositories and GitLab for our private repositories due to its easy to use features. Docker and Kubernetes are a must have for our highly scalable infrastructure complimented by HAProxy with Varnish in front of it. We are using a lot of npm and Visual Studio Code in our development sessions.

      See more

      Around the time of their Series A, Pinterest’s stack included Python and Django, with Tornado and Node.js as web servers. Memcached / Membase and Redis handled caching, with RabbitMQ handling queueing. Nginx, HAproxy and Varnish managed static-delivery and load-balancing, with persistent data storage handled by MySQL.

      See more
      Hazelcast logo

      Hazelcast

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

      related Hazelcast posts

      MongoDB logo

      MongoDB

      51.6K
      41.2K
      4K
      The database for giant ideas
      51.6K
      41.2K
      + 1
      4K
      PROS OF MONGODB
      • 822
        Document-oriented storage
      • 585
        No sql
      • 544
        Ease of use
      • 462
        Fast
      • 404
        High performance
      • 251
        Free
      • 212
        Open source
      • 177
        Flexible
      • 139
        Replication & high availability
      • 107
        Easy to maintain
      • 39
        Querying
      • 35
        Easy scalability
      • 34
        Auto-sharding
      • 33
        High availability
      • 29
        Map/reduce
      • 26
        Document database
      • 24
        Easy setup
      • 24
        Full index support
      • 15
        Reliable
      • 14
        Fast in-place updates
      • 13
        Agile programming, flexible, fast
      • 11
        No database migrations
      • 7
        Enterprise
      • 7
        Easy integration with Node.Js
      • 5
        Enterprise Support
      • 4
        Great NoSQL DB
      • 3
        Aggregation Framework
      • 3
        Drivers support is good
      • 3
        Support for many languages through different drivers
      • 2
        Schemaless
      • 2
        Managed service
      • 2
        Easy to Scale
      • 2
        Fast
      • 2
        Awesome
      • 1
        Consistent
      CONS OF MONGODB
      • 5
        Very slowly for connected models that require joins
      • 3
        Not acid compliant
      • 1
        Proprietary query language

      related MongoDB posts

      Jeyabalaji Subramanian

      Recently we were looking at a few robust and cost-effective ways of replicating the data that resides in our production MongoDB to a PostgreSQL database for data warehousing and business intelligence.

      We set ourselves the following criteria for the optimal tool that would do this job: - The data replication must be near real-time, yet it should NOT impact the production database - The data replication must be horizontally scalable (based on the load), asynchronous & crash-resilient

      Based on the above criteria, we selected the following tools to perform the end to end data replication:

      We chose MongoDB Stitch for picking up the changes in the source database. It is the serverless platform from MongoDB. One of the services offered by MongoDB Stitch is Stitch Triggers. Using stitch triggers, you can execute a serverless function (in Node.js) in real time in response to changes in the database. When there are a lot of database changes, Stitch automatically "feeds forward" these changes through an asynchronous queue.

      We chose Amazon SQS as the pipe / message backbone for communicating the changes from MongoDB to our own replication service. Interestingly enough, MongoDB stitch offers integration with AWS services.

      In the Node.js function, we wrote minimal functionality to communicate the database changes (insert / update / delete / replace) to Amazon SQS.

      Next we wrote a minimal micro-service in Python to listen to the message events on SQS, pickup the data payload & mirror the DB changes on to the target Data warehouse. We implemented source data to target data translation by modelling target table structures through SQLAlchemy . We deployed this micro-service as AWS Lambda with Zappa. With Zappa, deploying your services as event-driven & horizontally scalable Lambda service is dumb-easy.

      In the end, we got to implement a highly scalable near realtime Change Data Replication service that "works" and deployed to production in a matter of few days!

      See more
      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
      Couchbase logo

      Couchbase

      337
      439
      101
      Document-Oriented NoSQL Database
      337
      439
      + 1
      101
      PROS OF COUCHBASE
      • 18
        High performance
      • 17
        Flexible data model, easy scalability, extremely fast
      • 8
        Mobile app support
      • 6
        You can query it with Ansi-92 SQL
      • 5
        All nodes can be read/write
      • 4
        Open source, community and enterprise editions
      • 4
        Local cache capability
      • 4
        Both a key-value store and document (JSON) db
      • 4
        Equal nodes in cluster, allowing fast, flexible changes
      • 3
        Automatic configuration of sharding
      • 3
        SDKs in popular programming languages
      • 3
        Elasticsearch connector
      • 3
        Easy setup
      • 3
        Web based management, query and monitoring panel
      • 3
        Linearly scalable, useful to large number of tps
      • 3
        Easy cluster administration
      • 3
        Cross data center replication
      • 2
        NoSQL
      • 2
        DBaaS available
      • 2
        Map reduce views
      • 1
        FTS + SQL together
      CONS OF COUCHBASE
      • 3
        Terrible query language

      related Couchbase posts

      Gabriel Pa

      We implemented our first large scale EPR application from naologic.com using CouchDB .

      Very fast, replication works great, doesn't consume much RAM, queries are blazing fast but we found a problem: the queries were very hard to write, it took a long time to figure out the API, we had to go and write our own @nodejs library to make it work properly.

      It lost most of its support. Since then, we migrated to Couchbase and the learning curve was steep but all worth it. Memcached indexing out of the box, full text search works great.

      See more
      Gabriel Pa

      If you want to use Pouchdb might as well use RxDB which is an observables wrapper for Pouch but much more comfortable to use. Realm is awesome but Pouchdb and RxDB give you more control. You can use Couchbase (recommended) or CouchDB to enable 2-way sync

      See more
      Memcached Cloud logo

      Memcached Cloud

      13
      13
      24
      A fully-managed service for hosting and running your memcached in a reliable and fail-safe manner
      13
      13
      + 1
      24
      PROS OF MEMCACHED CLOUD
      • 6
        High-availability
      • 6
        Heroku add-on
      • 3
        Fast
      • 2
        Email alerts
      • 2
        Fail-safe
      • 1
        24/7 monitoring & support
      • 1
        Backups and import
      • 1
        Offered by Redis Labs
      • 1
        Auto-switchover
      • 1
        Seamless scalability
      CONS OF MEMCACHED CLOUD
        Be the first to leave a con

        related Memcached Cloud posts

        etcd logo

        etcd

        218
        287
        23
        A distributed consistent key-value store for shared configuration and service discovery
        218
        287
        + 1
        23
        PROS OF ETCD
        • 11
          Service discovery
        • 6
          Fault tolerant key value store
        • 2
          Bundled with coreos
        • 1
          Secure
        • 1
          Open Source
        • 1
          Privilege Access Management
        • 1
          Consol integration
        CONS OF ETCD
          Be the first to leave a con

          related etcd posts