Neo4j vs RabbitMQ

Overview

RabbitMQ

Stacks21.8K

Followers18.9K

Votes558

GitHub Stars13.2K

Forks4.0K

Neo4j

Stacks1.2K

Followers1.4K

Votes351

GitHub Stars15.3K

Forks2.5K

Neo4j vs RabbitMQ: What are the differences?

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; RabbitMQ: A messaging broker - an intermediary for messaging. RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

Neo4j can be classified as a tool in the "Graph Databases" category, while RabbitMQ is grouped under "Message Queue".

Some of the features offered by Neo4j are:

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

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

Robust messaging for applications
Easy to use
Runs on all major operating systems

"Cypher – graph query language" is the primary reason why developers consider Neo4j over the competitors, whereas "It's fast and it works with good metrics/monitoring" was stated as the key factor in picking RabbitMQ.

Neo4j and RabbitMQ are both open source tools. It seems that Neo4j with 6.61K GitHub stars and 1.63K forks on GitHub has more adoption than RabbitMQ with 5.95K GitHub stars and 1.78K GitHub forks.

According to the StackShare community, RabbitMQ has a broader approval, being mentioned in 940 company stacks & 548 developers stacks; compared to Neo4j, which is listed in 114 company stacks and 47 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 RabbitMQ, Neo4j

viradiya

Apr 12, 2020

Needs adviceon

AngularJS

ASP.NET Core

MSSQL

We are going to develop a microservices-based application. It consists of AngularJS, ASP.NET Core, and MSSQL.

We have 3 types of microservices. Emailservice, Filemanagementservice, Filevalidationservice

I am a beginner in microservices. But I have read about RabbitMQ, but come to know that there are Redis and Kafka also in the market. So, I want to know which is best.

933k views933k

Comments

Meili

Software engineer at Digital Science

Sep 24, 2020

Needs adviceon

ZeroMQ

RabbitMQ

Amazon SQS

Hi, we are in a ZMQ set up in a push/pull pattern, and we currently start to have more traffic and cases that the service is unavailable or stuck. We want to:

Not loose messages in services outages
Safely restart service without losing messages (@{ZeroMQ}|tool:1064| seems to need to close the socket in the receiver before restart manually)

Do you have experience with this setup with ZeroMQ? Would you suggest RabbitMQ or Amazon SQS (we are in AWS setup) instead? Something else?

Thank you for your time

500k views500k

Comments

André

Technology Manager at GS1 Portugal - Codipor

Jul 30, 2020

Needs adviceon

.NET Core

Hello dear developers, our company is starting a new project for a new Web App, and we are currently designing the Architecture (we will be using .NET Core). We want to embark on something new, so we are thinking about migrating from a monolithic perspective to a microservices perspective. We wish to containerize those microservices and make them independent from each other. Is it the best way for microservices to communicate with each other via ESB, or is there a new way of doing this? Maybe complementing with an API Gateway? Can you recommend something else different than the two tools I provided?

We want something good for Cost/Benefit; performance should be high too (but not the primary constraint).

Thank you very much in advance :)

461k views461k

Comments

Detailed Comparison

RabbitMQ	Neo4j
RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.	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.
Robust messaging for applications;Easy to use;Runs on all major operating systems;Supports a huge number of developer platforms;Open source and commercially supported	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
Statistics
GitHub Stars 13.2K	GitHub Stars 15.3K
GitHub Forks 4.0K	GitHub Forks 2.5K
Stacks 21.8K	Stacks 1.2K
Followers 18.9K	Followers 1.4K
Votes 558	Votes 351
Pros & Cons
Pros 235 It's fast and it works with good metrics/monitoring 80 Ease of configuration 60 I like the admin interface 52 Easy to set-up and start with 22 Durable Cons 9 Too complicated cluster/HA config and management 6 Needs Erlang runtime. Need ops good with Erlang runtime 5 Configuration must be done first, not by your code 4 Slow	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

What are some alternatives to RabbitMQ, Neo4j?

Kafka

Kafka is a distributed, partitioned, replicated commit log service. It provides the functionality of a messaging system, but with a unique design.

Celery

Celery is an asynchronous task queue/job queue based on distributed message passing. It is focused on real-time operation, but supports scheduling as well.

Amazon SQS

Transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. With SQS, you can offload the administrative burden of operating and scaling a highly available messaging cluster, while paying a low price for only what you use.

NSQ

NSQ is a realtime distributed messaging platform designed to operate at scale, handling billions of messages per day. It promotes distributed and decentralized topologies without single points of failure, enabling fault tolerance and high availability coupled with a reliable message delivery guarantee. See features & guarantees.

ActiveMQ

Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols, comes with easy to use Enterprise Integration Patterns and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License.

ZeroMQ

The 0MQ lightweight messaging kernel is a library which extends the standard socket interfaces with features traditionally provided by specialised messaging middleware products. 0MQ sockets provide an abstraction of asynchronous message queues, multiple messaging patterns, message filtering (subscriptions), seamless access to multiple transport protocols and more.

Apache NiFi

An easy to use, powerful, and reliable system to process and distribute data. It supports powerful and scalable directed graphs of data routing, transformation, and system mediation logic.

Gearman

Gearman allows you to do work in parallel, to load balance processing, and to call functions between languages. It can be used in a variety of applications, from high-availability web sites to the transport of database replication events.

Memphis

Highly scalable and effortless data streaming platform. Made to enable developers and data teams to collaborate and build real-time and streaming apps fast.

IronMQ

An easy-to-use highly available message queuing service. Built for distributed cloud applications with critical messaging needs. Provides on-demand message queuing with advanced features and cloud-optimized performance.

Related Comparisons

Some of the features offered by Neo4j are:

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

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

Robust messaging for applications
Easy to use
Runs on all major operating systems

Neo4j vs RabbitMQ