Is there a drawback for using Aerospike when used in non-SSD server?

  • 1
    Aerospike claims it's an in-memory database. So why would the harddisk play any role if everything is in memory?
    – user1822
    Commented Nov 28, 2014 at 7:49
  • because it provides hdd persistence feature
    – Kokizzu
    Commented Nov 28, 2014 at 7:53
  • Its a misconception that aerospike is an in-memory database, unless you call SSDs "memory". It's an flash-optimized database which is intended to exceed RAM, unlike Redis. Redis uses disk for persistence only - in Aerospike all the indexes need to fit in memory but since you can easily cluster, it's much easier to do than Redis. It's unfortunate that this is closed because it's a good question. It might be better reworded like "what are the performance impacts of using aerospike with a non-ssd?" Aerospike is written specifically to take advantage of SSD, so it's a good question.
    – Yehosef
    Commented May 31, 2015 at 13:41
  • In all fairness, even Aerospike advertises itself as an in-memory database. From aerospike.com/products-services - "Aerospike has Open Sourced its revolutionary in-memory NoSQL database and key-value store technology." - but I think this is more of a marketing ploy - the next line says "Because Aerospike is flash-optimized with a hybrid RAM/SSD storage architecture, you can get 10x better performance while using 10x fewer servers."
    – Yehosef
    Commented May 31, 2015 at 13:45

1 Answer 1


Not at all! Aerospike is a great in-memory key-value store, typically as fast as Redis, but that also scales super easy.

You can check the different configurations possible on Aerospike here. So if you can fit all your data in memory, Aerospike will work as well or better then any other in-memory database. The SSD optimization is useful for larger data sets that would be too expensive to fully store in memory and Aerospike is also optimized for that use case.

  • ah, let me clarify, what I mean by non-SSD is conventional harddisk (magnetic)
    – Kokizzu
    Commented Nov 28, 2014 at 7:29
  • 3
    Got it, I misunderstood. Well, you will not get anywhere close to the performance you would achieve on SSD if you go with rotational (magnetic) HDs and you may also wear them faster then SSD. (Actually different SSDs also perform at different levels). You can use rotational drives for persisting a 'data in memory' configuration though given the very different access pattern in that case. You can read more about the details on the following links: aerospike.com/docs/architecture/storage.html and aerospike.com/docs/operations/plan/ssd
    – meher
    Commented Nov 29, 2014 at 17:24
  • you can see performance comparison of redis to aerospike at aerospike.com/when-to-use-aerospike-vs-redis - since it's threaded, it can reach higher throughput without manual sharding.
    – Yehosef
    Commented May 31, 2015 at 13:46

Not the answer you're looking for? Browse other questions tagged or ask your own question.