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

Aerospike

149
209
+ 1
36
Redis

43.4K
32.4K
+ 1
3.9K
Add tool

Aerospike vs Redis: What are the differences?

Aerospike: 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; Redis: An in-memory database that persists on disk. 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.

Aerospike and Redis belong to "In-Memory Databases" category of the tech stack.

"Ram and/or ssd persistence " is the primary reason why developers consider Aerospike over the competitors, whereas "Performance" was stated as the key factor in picking Redis.

Aerospike and Redis are both open source tools. It seems that Redis with 37.4K GitHub stars and 14.4K forks on GitHub has more adoption than Aerospike with 295 GitHub stars and 54 GitHub forks.

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

Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Aerospike
Pros of Redis
  • 11
    Ram and/or ssd persistence
  • 10
    Easy clustering support
  • 5
    Easy setup
  • 3
    Acid
  • 2
    Performance better than Redis
  • 2
    Petabyte Scale
  • 2
    Scale
  • 1
    Ease of use
  • 875
    Performance
  • 535
    Super fast
  • 511
    Ease of use
  • 441
    In-memory cache
  • 321
    Advanced key-value cache
  • 190
    Open source
  • 179
    Easy to deploy
  • 163
    Stable
  • 153
    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

Sign up to add or upvote prosMake informed product decisions

Cons of Aerospike
Cons of Redis
    Be the first to leave a con
    • 14
      Cannot query objects directly
    • 2
      No secondary indexes for non-numeric data types
    • 1
      No WAL

    Sign up to add or upvote consMake informed product decisions