Need advice about which tool to choose?Ask the StackShare community!

Aerospike

152
213
+ 1
45
Memcached

5.9K
4.2K
+ 1
469
Add tool

Aerospike vs Memcached: What are the differences?

Developers describe Aerospike as "Flash-optimized in-memory open source NoSQL database". 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. On the other hand, Memcached is detailed as "High-performance, distributed memory object caching system". 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.

Aerospike and Memcached are primarily classified as "In-Memory Databases" and "Databases" tools respectively.

"Ram and/or ssd persistence " is the top reason why over 9 developers like Aerospike, while over 133 developers mention "Fast object cache" as the leading cause for choosing Memcached.

Aerospike and Memcached are both open source tools. It seems that Memcached with 9K GitHub stars and 2.6K forks on GitHub has more adoption than Aerospike with 296 GitHub stars and 55 GitHub forks.

According to the StackShare community, Memcached has a broader approval, being mentioned in 755 company stacks & 267 developers stacks; compared to Aerospike, which is listed in 30 company stacks and 9 developer stacks.

Decisions about Aerospike and Memcached
 This was roughly 4 years ago at this point. We had been using an old iteration of memcache on Windows as the data cache per server for while and had for whatever reason opted to store our session data (to which the application is heavily dependent) in App Fabric. App Fabric had come to EOL and we needed to move away from it. As a quick search showed throughput capacity to be higher and overall features of Redis were better we initially implemented it. The number of changes required were minimal and we were able to migrate away to a more resilient system pretty quickly.
 We hit a snag in that the implementation of the Redis session handler at that point only took a single IP so we had to do use keepalived and HAProxy to display the application consistently between master and slave failovers. This caused issues on occasion of dropped connections to the backend service. We upgraded our client and could put both members into our config files and it stopped timing out. We were all happy in this and it was (for it's own part) a significant upgrade. Generally performance was better for all pages. 
 We found however, that our application was serializing all requests and locking on the thread via session lock for a great many things and this caused us and our users considerable headaches on occasion. We found that the implementation of the couchbase session handler gave us the option of ignoring session write locks and not be required to rewrite dozens of pages to handle the no session requirement as the application was working fine without the need to be threadsafe. Though the maximum throughput was not as good compared to Redis the application performance was considerably better as a result of the change. The multi-master write was a big benefit and the cross data center replication was a nice thing to have as that would allow our users to remain logged in even across DataCenter fail-over events (praying that never happened). Overall we used that for session handling and chose to use couchbase (in a 2nd cluster) to handle memcache requests as that gave us greater capacity to handle larger objects more efficiently. 
 We are, all these years later, looking to move into the newer features of couchbase to give us more and better use of this product that really has been the answer to a bunch of the growing pains we experienced. Since the decision performance has not been on wild rides and stability has never been better. So I sing the praises of couchbase to anyone that will listen.
See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Aerospike
Pros of Memcached
  • 14
    Ram and/or ssd persistence
  • 11
    Easy clustering support
  • 5
    Easy setup
  • 4
    Acid
  • 3
    Petabyte Scale
  • 3
    Scale
  • 3
    Performance better than Redis
  • 2
    Ease of use
  • 137
    Fast object cache
  • 128
    High-performance
  • 90
    Stable
  • 65
    Mature
  • 33
    Distributed caching system
  • 11
    Improved response time and throughput
  • 3
    Great for caching HTML
  • 2
    Putta

Sign up to add or upvote prosMake informed product decisions

Cons of Aerospike
Cons of Memcached
    Be the first to leave a con
    • 2
      Only caches simple types

    Sign up to add or upvote consMake informed product decisions

    What is 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.

    What is Memcached?

    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.

    Need advice about which tool to choose?Ask the StackShare community!

    What companies use Aerospike?
    What companies use Memcached?
    See which teams inside your own company are using Aerospike or Memcached.
    Sign up for Private StackShareLearn More

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with Aerospike?
    What tools integrate with Memcached?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    Blog Posts

    Dec 22 2020 at 9:26PM

    Pinterest

    Amazon EC2C langMemcached+4
    10
    2393
    Jun 6 2019 at 5:11PM

    AppSignal

    RedisRubyKafka+9
    15
    1220
    GitHubDockerReact+17
    34
    30967
    GitHubPythonNode.js+47
    52
    69833
    JavaScriptGitHubNode.js+26
    19
    4683
    JavaScriptGitHubPython+42
    52
    20009
    GitHubPythonSlack+25
    7
    2927
    What are some alternatives to Aerospike and Memcached?
    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.
    Riak
    Riak is a distributed database designed to deliver maximum data availability by distributing data across multiple servers. As long as your client can reach one Riak server, it should be able to write data. In most failure scenarios, the data you want to read should be available, although it may not be the most up-to-date version of that data.
    Cassandra
    Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.
    Elasticsearch
    Elasticsearch is a distributed, RESTful search and analytics engine capable of storing data and searching it in near real time. Elasticsearch, Kibana, Beats and Logstash are the Elastic Stack (sometimes called the ELK Stack).
    Tarantool
    It is designed to give you the flexibility, scalability, and performance that you want, as well as the reliability and manageability that you need in mission-critical applications
    See all alternatives