Looking for clarity on Event Hubs vs Topics in Azure Service Bus
Looking for clarity on Event Hubs vs Topics in Azure Service Bus
Looking for clarity on Event Hubs vs Topics in Azure Service Bus
Re: Looking for clarity on Event Hubs vs Topics in Azure Service Bus
Correct!!
The fundamental difference between EventHubs and Topics is - TOPICS offer **per-message semantics** - whereas, EventHubs - offer **Stream Semantics** - implies, one should not expect any `per-message` feature/semantics with EventHubs.
Any middle-tier providing `per-message` features comes with the `processing overhead (the tax)`!!
For Ex: Per message Duplicate detection, Receive confirmation per message (topics have a Message.Complete to ack Msg received) - are all Topic features. EventHubs narrows-down the feature set to provide a better low-latency/high-throughput solution.
To visualize features like at-least-once delivery (of per msg is not available in EventHubs) is to translate it to stream semantics - Read until a point in a Given eventHub partition and checkpoint and let your application which is consuming those events handle the `at-least-once` delivery.
[more on Event Hubs...](https://medium.com/@sreeramg/what-is-microsoft-azure-event-hubs-1ec100452067)
The fundamental difference between EventHubs and Topics is - TOPICS offer **per-message semantics** - whereas, EventHubs - offer **Stream Semantics** - implies, one should not expect any `per-message` feature/semantics with EventHubs.
Any middle-tier providing `per-message` features comes with the `processing overhead (the tax)`!!
For Ex: Per message Duplicate detection, Receive confirmation per message (topics have a Message.Complete to ack Msg received) - are all Topic features. EventHubs narrows-down the feature set to provide a better low-latency/high-throughput solution.
To visualize features like at-least-once delivery (of per msg is not available in EventHubs) is to translate it to stream semantics - Read until a point in a Given eventHub partition and checkpoint and let your application which is consuming those events handle the `at-least-once` delivery.
[more on Event Hubs...](https://medium.com/@sreeramg/what-is-microsoft-azure-event-hubs-1ec100452067)