Azure Service Bus vs ejabberd

Overview

ejabberd

Stacks33

Followers48

Votes0

GitHub Stars6.5K

Forks1.5K

Azure Service Bus

Stacks553

Followers536

Votes7

Azure Service Bus vs ejabberd: What are the differences?

Developers describe Azure Service Bus as "*Reliable cloud messaging as a service (MaaS) *". It is a cloud messaging system for connecting apps and devices across public and private clouds. You can depend on it when you need highly-reliable cloud messaging service between applications and services, even when one or more is offline. On the other hand, ejabberd is detailed as "A scalable and robust instant messaging server". It is a distributed, fault-tolerant technology that allows the creation of large-scale instant messaging applications. The server can reliably support thousands of simultaneous users on a single node and has been designed to provide exceptional standards of fault tolerance.

Azure Service Bus and ejabberd belong to "Message Queue" category of the tech stack.

ejabberd is an open source tool with 4.18K GitHub stars and 1.25K GitHub forks. Here's a link to ejabberd's open source repository on GitHub.

Yammer, OneWire, and eMarketer, Inc. are some of the popular companies that use Azure Service Bus, whereas ejabberd is used by AppScale Systems, KongHack Inc., and UrbanClap. Azure Service Bus has a broader approval, being mentioned in 11 company stacks & 8 developers stacks; compared to ejabberd, which is listed in 5 company stacks and 3 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 ejabberd, Azure Service Bus

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

ejabberd	Azure Service Bus
It is a distributed, fault-tolerant technology that allows the creation of large-scale instant messaging applications. The server can reliably support thousands of simultaneous users on a single node and has been designed to provide exceptional standards of fault tolerance.	It is a cloud messaging system for connecting apps and devices across public and private clouds. You can depend on it when you need highly-reliable cloud messaging service between applications and services, even when one or more is offline.
Cross-platform; Administrator-friendly; Internationalized; Fault-tolerant	-
Statistics
GitHub Stars 6.5K	GitHub Stars -
GitHub Forks 1.5K	GitHub Forks -
Stacks 33	Stacks 553
Followers 48	Followers 536
Votes 0	Votes 7
Pros & Cons
No community feedback yet	Pros 4 Easy Integration with .Net 2 Cloud Native 1 Use while high messaging need Cons 1 Skills can only be used in Azure - vendor lock-in 1 Observability of messages in the queue is lacking 1 Limited features in Basic tier 1 Lacking in JMS support
Integrations
PostgreSQL Linux MySQL Mac OS X	No integrations available

What are some alternatives to ejabberd, Azure Service Bus?

Kafka

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

RabbitMQ

RabbitMQ gives your applications a common platform to send and receive messages, and your messages a safe place to live until received.

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.