Hi Adam
No problem, I'm glad you had a good break :)
I think the goals and tradeoffs that Hermes chose provide a useful system,
I'm just not sure reliable is quite the right word to use when describing
it. When I think of 'reliable' in the context of a message queue I think of
guaranteed
Thanks for the feedback. We will improve our documentation to make it clear
what guarantees we concentrate on and what are the tradeoffs. And think of
some catchy way to describe the system :)
2015-05-25 10:02 GMT+02:00 Daniel Compton daniel.compton.li...@gmail.com:
Hi Adam
No problem, I'm
Hi Daniel,
First of all sorry for late response, i enjoyed short vacation :)
I guess the documentation might be bit misleading here, and so we should
improve it: we do not aim (and can't) provide higher guarantees than Kafka.
We want to be as bullteproofs as possible in REST interface segments.
Hi Adam
Firstly, thanks for open sourcing this, it looks like a great tool and I
can imagine a lot of people will find it very useful.
I had a few thoughts reading the docs. I may have misunderstood things but
it seems that your goal of meeting a strict SLA conflicts with your goal of
Hello everyone,
I'm technical team lead of Hermes project. I will try to answer already
posted questions, but feel free to ask me anything.
1) Can you comment on how this compares to Confluent's REST proxy?
We do not perceive Hermes as mere proxy. While Confluent product wants to
help services
Interesting. Thanks for sharing and working on this!
Can you comment on how this compares to Confluent's REST proxy?
On Sat, May 16, 2015 at 12:01 AM, Marcin Kuthan marcin.kut...@gmail.com
wrote:
Hi Everyone
Hermes is an asynchronous message broker built on top of Kafka. It
provides
Hi Stevo
Thank's for your comment.
On 16 May 2015 at 17:43, Stevo Slavić ssla...@gmail.com wrote:
Nice, thanks for sharing!
Is 30k msgs/sec publishing or push throughput? Will check, hopefully
performance tests are included in sources.
30k msgs/sec is our regular traffic handled by hermes
Hi Warren
With Hermes, the publisher is never blocked. Even if message has not
been sent to Kafka cluster, or if message has been sent but not
acknowledged. It is especially useful if your system needs to have
strict SLA guarantees.
From the consumers perspective there is retrying policy if the
Nice, thanks for sharing!
Is 30k msgs/sec publishing or push throughput? Will check, hopefully
performance tests are included in sources.
Does Hermes have same max number of topics limitations as Kafka or does it
include a solution to have that aspect scalable as well?
On May 16, 2015 8:02 AM,
Hi Everyone
Hermes is an asynchronous message broker built on top of Kafka. It
provides reliable, fault tolerant REST interface for message
publishing and adaptive push mechanisms for message sending. Hermes is
used as a message broker for asynchronous communication between
microservices.
Some
10 matches
Mail list logo
