Any advantage of using Vertx. EventBus?

[VN]

Hi,

Vert.x is really awesome, but it has a lot of features that overlap with other frameworks. One example of these is EventBus. There are already a lot of messaging frameworks out there such as ActiveMQ, RabbitMQ, Kafka, ZeroMQ and even Hazelcast the underlying cluster manager of Vertx.x also provides messaging features. So, what makes Vert.x's EventBus different from them and how does it compare to them in terms of performance and reliability? Are there any benchmarks done before?

[Jochen Mader]

The options you mentioned are all very different beasts.

First about Vert.x-Eventbus:

It is by default distributed und broker-less so it doesn't require centralized infrastructure. There are no delivery guarantees for events being sent over it.

The others:

- ActiveMQ: Brokercentric multi purpose message broker. Supports Pub/Sub and Pub/Sub/Callback and guaranteed delivery. It supports many standard messaging protocols, most importantly JMS, AMQP and MQTT
- RabbitMQ: Brokercentric multi purpose message broker. Supports Pub/Sub and Pub/Sub/Callback and guaranteed delivery. It supports many standard messaging protocols, most importantly JMS, AMQP and MQTT

- Kafka: Brokercentric, highly opinionated Pub/Sub implementation. No delivery guarantees. People often produce a brutal mess by
        a) not realizing what Kafka is built for
        b) not spending enough time understanding the way it is builkd (which you have to to use it correctly)

- ZeroMQ: This more a specification than an actual bus. There are tons of implementations for all kinds of different platforms. Very low footprint in RAM and on the network. But it's basically "build your own" eventbus. Even if you don't use it I suggest reading the documentation as it covers so many areas of distributed systems.

- Hazelcast: I never used their eventbus.

There is no silver bullet, take a look at the problem you have to solve and pick the right solution to solve it :)

2017-02-15 4:20 GMT+01:00 VN <ngan.v...@gmail.com>:

Hi,

Vert.x is really awesome, but it has a lot of features that overlap with other frameworks. One example of these is EventBus. There are already a lot of messaging frameworks out there such as ActiveMQ, RabbitMQ, Kafka, ZeroMQ and even Hazelcast the underlying cluster manager of Vertx.x also provides messaging features. So, what makes Vert.x's EventBus different from them and how does it compare to them in terms of performance and reliability? Are there any benchmarks done before?

--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vertx+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/vertx.
To view this discussion on the web, visit https://groups.google.com/d/msgid/vertx/0b1a741f-072c-4584-ae68-698f20759068%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Jochen Mader | Lead IT Consultant

codecentric AG | Elsenheimerstr. 55a | 80687 München | Deutschland
tel: +49 89 215486633 | fax: +49 89 215486699 | mobil: +49 152 51862390
www.codecentric.de | blog.codecentric.de | www.meettheexperts.de

Sitz der Gesellschaft: Düsseldorf | HRB 63043 | Amtsgericht Düsseldorf
Vorstand: Michael Hochgürtel . Rainer Vehns
Aufsichtsrat: Patric Fedlmeier (Vorsitzender) . Klaus Jäger . Jürgen Schütz

[javadevmtl]

Also to mention the vertx eventbus is mostly uawd for inter vertx "module" (verticles) communications mostly, even though it can bridge with other frameworks and languages. And it can also bridge with the browser so you can create a cluster of browsers also.