Hazelcast vs Neo4j

Overview

Neo4j

Stacks1.2K

Followers1.4K

Votes351

GitHub Stars15.3K

Forks2.5K

Hazelcast

Stacks427

Followers474

Votes59

GitHub Stars6.4K

Forks1.9K

Hazelcast vs Neo4j: What are the differences?

Hazelcast: Clustering and highly scalable data distribution platform for Java. 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; Neo4j: The world’s leading Graph Database. Neo4j stores data in nodes connected by directed, typed relationships with properties on both, also known as a Property Graph. It is a high performance graph store with all the features expected of a mature and robust database, like a friendly query language and ACID transactions.

Hazelcast belongs to "In-Memory Databases" category of the tech stack, while Neo4j can be primarily classified under "Graph Databases".

Some of the features offered by Hazelcast are:

Distributed implementations of java.util.{Queue, Set, List, Map}
Distributed implementation of java.util.concurrent.locks.Lock
Distributed implementation of java.util.concurrent.ExecutorService

On the other hand, Neo4j provides the following key features:

intuitive, using a graph model for data representation
reliable, with full ACID transactions
durable and fast, using a custom disk-based, native storage engine

"High Availibility" is the primary reason why developers consider Hazelcast over the competitors, whereas "Cypher – graph query language" was stated as the key factor in picking Neo4j.

Hazelcast and Neo4j are both open source tools. Neo4j with 6.6K GitHub stars and 1.63K forks on GitHub appears to be more popular than Hazelcast with 3.18K GitHub stars and 1.16K GitHub forks.

Medium, Movielala, and Hinge are some of the popular companies that use Neo4j, whereas Hazelcast is used by Yammer, Seat Pagine Gialle, and Para. Neo4j has a broader approval, being mentioned in 114 company stacks & 47 developers stacks; compared to Hazelcast, which is listed in 26 company stacks and 16 developer stacks.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Neo4j, Hazelcast

Jaime

none at none

Aug 31, 2020

Needs advice

Hi, I want to create a social network for students, and I was wondering which of these three Oriented Graph DB's would you recommend. I plan to implement machine learning algorithms such as k-means and others to give recommendations and some basic data analyses; also, everything is going to be hosted in the cloud, so I expect the DB to be hosted there. I want the queries to be as fast as possible, and I like good tools to monitor my data. I would appreciate any recommendations or thoughts.

Context:

I released the MVP 6 months ago and got almost 600 users just from my university in Colombia, But now I want to expand it all over my country. I am expecting more or less 20000 users.

56.4k views56.4k

Comments

Detailed Comparison

Neo4j	Hazelcast
Neo4j stores data in nodes connected by directed, typed relationships with properties on both, also known as a Property Graph. It is a high performance graph store with all the features expected of a mature and robust database, like a friendly query language and ACID transactions.	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.
intuitive, using a graph model for data representation;reliable, with full ACID transactions;durable and fast, using a custom disk-based, native storage engine;massively scalable, up to several billion nodes/relationships/properties;highly-available, when distributed across multiple machines;expressive, with a powerful, human readable graph query language;fast, with a powerful traversal framework for high-speed graph queries;embeddable, with a few small jars;simple, accessible by a convenient REST interface or an object-oriented Java API	Distributed implementations of java.util.{Queue, Set, List, Map};Distributed implementation of java.util.concurrent.locks.Lock;Distributed implementation of java.util.concurrent.ExecutorService;Distributed MultiMap for one-to-many relationships;Distributed Topic for publish/subscribe messaging;Synchronous (write-through) and asynchronous (write-behind) persistence;Transaction support;Socket level encryption support for secure clusters;Second level cache provider for Hibernate;Monitoring and management of the cluster via JMX;Dynamic HTTP session clustering;Support for cluster info and membership events;Dynamic discovery, scaling, partitioning with backups and fail-over
Statistics
GitHub Stars 15.3K	GitHub Stars 6.4K
GitHub Forks 2.5K	GitHub Forks 1.9K
Stacks 1.2K	Stacks 427
Followers 1.4K	Followers 474
Votes 351	Votes 59
Pros & Cons
Pros 69 Cypher – graph query language 61 Great graphdb 33 Open source 31 Rest api 27 High-Performance Native API Cons 9 Comparably slow 4 Can't store a vertex as JSON 1 Doesn't have a managed cloud service at low cost	Pros 11 High Availibility 6 Distributed compute 6 Distributed Locking 5 Sharding 4 Load balancing Cons 4 License needed for SSL
Integrations
No integrations available	Java Spring

What are some alternatives to Neo4j, Hazelcast?

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.

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.

MemSQL

MemSQL converges transactions and analytics for sub-second data processing and reporting. Real-time businesses can build robust applications on a simple and scalable infrastructure that complements and extends existing data pipelines.

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

SAP HANA

It is an application that uses in-memory database technology that allows the processing of massive amounts of real-time data in a short time. The in-memory computing engine allows it to process data stored in RAM as opposed to reading it from a disk.

VoltDB

VoltDB is a fundamental redesign of the RDBMS that provides unparalleled performance and scalability on bare-metal, virtualized and cloud infrastructures. VoltDB is a modern in-memory architecture that supports both SQL + Java with data durability and fault tolerance.

Dgraph

Dgraph's goal is to provide Google production level scale and throughput, with low enough latency to be serving real time user queries, over terabytes of structured data. Dgraph supports GraphQL-like query syntax, and responds in JSON and Protocol Buffers over GRPC and HTTP.

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

Azure Redis Cache

It perfectly complements Azure database services such as Cosmos DB. It provides a cost-effective solution to scale read and write throughput of your data tier. Store and share database query results, session states, static contents, and more using a common cache-aside pattern.

RedisGraph

RedisGraph is a graph database developed from scratch on top of Redis, using the new Redis Modules API to extend Redis with new commands and capabilities. Its main features include: - Simple, fast indexing and querying - Data stored in RAM, using memory-efficient custom data structures - On disk persistence - Tabular result sets - Simple and popular graph query language (Cypher) - Data Filtering, Aggregation and ordering

Related Comparisons

Some of the features offered by Hazelcast are:

Distributed implementations of java.util.{Queue, Set, List, Map}
Distributed implementation of java.util.concurrent.locks.Lock
Distributed implementation of java.util.concurrent.ExecutorService

On the other hand, Neo4j provides the following key features:

intuitive, using a graph model for data representation
reliable, with full ACID transactions
durable and fast, using a custom disk-based, native storage engine

"High Availibility" is the primary reason why developers consider Hazelcast over the competitors, whereas "Cypher – graph query language" was stated as the key factor in picking Neo4j.

Hazelcast vs Neo4j