Need advice about which tool to choose?Ask the StackShare community!
Apache Ignite vs Redis: What are the differences?
Developers describe Apache Ignite as "An open-source distributed database, caching and processing platform *". It is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale. On the other hand, *Redis** is detailed as "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.
Apache Ignite and Redis belong to "In-Memory Databases" category of the tech stack.
Apache Ignite and Redis are both open source tools. It seems that Redis with 37.9K GitHub stars and 14.6K forks on GitHub has more adoption than Apache Ignite with 2.67K GitHub stars and 1.3K GitHub forks.
According to the StackShare community, Redis has a broader approval, being mentioned in 4259 company stacks & 8884 developers stacks; compared to Apache Ignite, which is listed in 4 company stacks and 4 developer stacks.
Pros of Apache Ignite
- Written in java. runs on jvm4
- Free4
- Load balancing3
- Multiple client language support3
- Sql query support in cluster wide3
- Rest interface3
- High Avaliability3
- Better Documentation2
- Easy to use2
- Distributed compute1
- Distributed Locking1
Pros of Redis
- Performance879
- Super fast536
- Ease of use511
- In-memory cache441
- Advanced key-value cache321
- Open source190
- Easy to deploy179
- Stable163
- Free152
- Fast120
- High-Performance40
- High Availability39
- Data Structures34
- Very Scalable32
- Replication23
- Great community20
- Pub/Sub19
- "NoSQL" key-value data store17
- Hashes14
- Sets12
- Sorted Sets10
- Lists9
- BSD licensed8
- NoSQL8
- Async replication7
- Integrates super easy with Sidekiq for Rails background7
- Bitmaps7
- Open Source6
- Keys with a limited time-to-live6
- Strings5
- Lua scripting5
- Awesomeness for Free!4
- Hyperloglogs4
- outstanding performance3
- Runs server side LUA3
- Networked3
- LRU eviction of keys3
- Written in ANSI C3
- Feature Rich3
- Transactions3
- Data structure server2
- Performance & ease of use2
- Existing Laravel Integration1
- Automatic failover1
- Easy to use1
- Object [key/value] size each 500 MB1
- Simple1
- Channels concept1
- Scalable1
- Temporarily kept on disk1
- Dont save data if no subscribers are found1
- Jk0
Sign up to add or upvote prosMake informed product decisions
Cons of Apache Ignite
Cons of Redis
- Cannot query objects directly14
- No secondary indexes for non-numeric data types2
- No WAL1