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
consumer is not able to handle published message. In addition, Hermes
is able to adjust speed of sending messages to actual situation (i.e.
subscribing service has slown down due to heavy GC)


On 18 May 2015 at 09:56, Warren Henning <warren.henn...@gmail.com> wrote:
> 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 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 of the main features:
>>
>> - Performance and scalability - Hermes in production handling up to
>> 30.000 msgs/sec with 99.9th percentile latency below 100 ms on a
>> 4-node cluster.
>>
>> - Reliability - Hermes is used for publishing sensitive data, such as
>> billing events, user account changes etc. Hermes allows to define more
>> reliable policy for those important events - require acknowledge from
>> all Kafka replicas and increase request timeouts.
>>
>> - Push model - It makes receiving messages from Hermes dead simple:
>> you just have to write one HTTP endpoint in your service. It’s up to
>> Hermes to create Kafka consumer, redeliver messages, keep eye on
>> throughput limits etc.
>>
>> Feedback and comments are welcome, you can find Hermes documentation at:
>> http://hermes-pubsub.readthedocs.org/en/latest/index.html
>>
>> Hermes is published under Apache Licence:
>> https://github.com/allegro/hermes
>>
>> Best Regards,
>> Marcin
>>

Reply via email to