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

Hazelcast

346
469
+ 1
59
LokiJS

36
55
+ 1
3
Redis

58.1K
44.7K
+ 1
3.9K

Hazelcast vs LokiJS vs Redis: What are the differences?

# Introduction

Key differences between Hazelcast, LokiJS, and Redis are outlined below:

1. **Data Storage and Retrieval**: Hazelcast is a distributed, in-memory data grid that provides high-performance data storage and retrieval for large volumes of data. LokiJS, on the other hand, is an in-memory database that stores data in JavaScript objects and operates locally within the browser, making it suitable for small-scale applications. Redis, a popular open-source in-memory data structure store, offers versatile data storage capabilities, including caching, messaging, and real-time analytics.

2. **Data Persistence**: While Hazelcast and Redis support data persistence to disk, allowing data to be stored even after system restarts, LokiJS focuses primarily on in-memory operations and does not offer built-in disk persistence. This distinction makes Hazelcast and Redis more suitable for applications requiring durable data storage and recovery in case of failures.

3. **Scalability and Performance**: Hazelcast is designed for horizontal scalability by distributing data across multiple nodes in a cluster, ensuring high performance and low latency. In contrast, LokiJS and Redis can scale vertically by deploying on more powerful hardware but may encounter limitations in handling massive datasets compared to Hazelcast's distributed architecture.

4. **Data Querying and Indexing**: While Redis supports indexing and querying of data using a variety of data structures like sets, lists, and sorted sets, Hazelcast focuses on distributed data processing and event-driven architecture rather than traditional database querying functionalities. LokiJS provides basic querying capabilities but may not match the performance of Redis for complex data operations.

5. **Programming Language Support**: Hazelcast and Redis offer client libraries for various programming languages, making it easier for developers to integrate these databases into their applications. LokiJS, being tailored for JavaScript environments, provides native support for JavaScript objects and libraries but may require additional effort for integration with other programming languages.

6. **Community Ecosystem and Support**: Redis has a robust community ecosystem with extensive documentation, tutorials, and community plugins available for developers. Hazelcast also has a dedicated community and commercial support options, whereas LokiJS, being a more niche solution, may have limited community resources and support avenues available to users.

In Summary, the key differences between Hazelcast, LokiJS, and Redis lie in their data storage mechanisms, persistence capabilities, scalability, querying functionalities, programming language support, and community support ecosystems.
Get Advice from developers at your company using StackShare Enterprise. Sign up for StackShare Enterprise.
Learn More
Pros of Hazelcast
Pros of LokiJS
Pros of Redis
  • 11
    High Availibility
  • 6
    Distributed Locking
  • 6
    Distributed compute
  • 5
    Sharding
  • 4
    Load balancing
  • 3
    Map-reduce functionality
  • 3
    Simple-to-use
  • 3
    Written in java. runs on jvm
  • 3
    Publish-subscribe
  • 3
    Sql query support in cluster wide
  • 2
    Optimis locking for map
  • 2
    Performance
  • 2
    Multiple client language support
  • 2
    Rest interface
  • 1
    Admin Interface (Management Center)
  • 1
    Better Documentation
  • 1
    Easy to use
  • 1
    Super Fast
  • 3
    Can query the objects directly
  • 886
    Performance
  • 542
    Super fast
  • 513
    Ease of use
  • 444
    In-memory cache
  • 324
    Advanced key-value cache
  • 194
    Open source
  • 182
    Easy to deploy
  • 164
    Stable
  • 155
    Free
  • 121
    Fast
  • 42
    High-Performance
  • 40
    High Availability
  • 35
    Data Structures
  • 32
    Very Scalable
  • 24
    Replication
  • 22
    Great community
  • 22
    Pub/Sub
  • 19
    "NoSQL" key-value data store
  • 16
    Hashes
  • 13
    Sets
  • 11
    Sorted Sets
  • 10
    NoSQL
  • 10
    Lists
  • 9
    Async replication
  • 9
    BSD licensed
  • 8
    Bitmaps
  • 8
    Integrates super easy with Sidekiq for Rails background
  • 7
    Keys with a limited time-to-live
  • 7
    Open Source
  • 6
    Lua scripting
  • 6
    Strings
  • 5
    Awesomeness for Free
  • 5
    Hyperloglogs
  • 4
    Transactions
  • 4
    Outstanding performance
  • 4
    Runs server side LUA
  • 4
    LRU eviction of keys
  • 4
    Feature Rich
  • 4
    Written in ANSI C
  • 4
    Networked
  • 3
    Data structure server
  • 3
    Performance & ease of use
  • 2
    Dont save data if no subscribers are found
  • 2
    Automatic failover
  • 2
    Easy to use
  • 2
    Temporarily kept on disk
  • 2
    Scalable
  • 2
    Existing Laravel Integration
  • 2
    Channels concept
  • 2
    Object [key/value] size each 500 MB
  • 2
    Simple

Sign up to add or upvote prosMake informed product decisions

Cons of Hazelcast
Cons of LokiJS
Cons of Redis
  • 4
    License needed for SSL
    Be the first to leave a con
    • 15
      Cannot query objects directly
    • 3
      No secondary indexes for non-numeric data types
    • 1
      No WAL

    Sign up to add or upvote consMake informed product decisions

    - No public GitHub repository available -

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

    What is LokiJS?

    LokiJS is a document oriented database written in javascript, published under MIT License. Its purpose is to store javascript objects as documents in a nosql fashion and retrieve them with a similar mechanism. Runs in node (including cordova/phonegap and node-webkit), nativescript and the browser.

    What is Redis?

    Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.

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

    Jobs that mention Hazelcast, LokiJS, and Redis as a desired skillset
    LaunchDarkly
    Oakland, California, United States
    What companies use Hazelcast?
    What companies use LokiJS?
    What companies use Redis?

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

    What tools integrate with Hazelcast?
    What tools integrate with LokiJS?
    What tools integrate with Redis?

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

    Blog Posts

    Nov 20 2019 at 3:38AM

    OneSignal

    PostgreSQLRedisRuby+8
    9
    4639
    Jun 6 2019 at 5:11PM

    AppSignal

    RedisRubyKafka+9
    15
    1639
    GitHubDockerReact+17
    40
    36247
    What are some alternatives to Hazelcast, LokiJS, and Redis?
    Apache Spark
    Spark is a fast and general processing engine compatible with Hadoop data. It can run in Hadoop clusters through YARN or Spark's standalone mode, and it can process data in HDFS, HBase, Cassandra, Hive, and any Hadoop InputFormat. It is designed to perform both batch processing (similar to MapReduce) and new workloads like streaming, interactive queries, and machine learning.
    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.
    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.
    Apache Ignite
    It is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at petabyte scale
    RabbitMQ
    RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.
    See all alternatives