Episode 160: Event Hubs with Elio Damaggio

Play Episode 160: Event Hubs with Elio Damaggio

The Discussion

  • User profile image


    device id can be used as partition id does this mean that the number of devices is limited by the number of partitions (max 32)?

  • User profile image

    In which cases should you use events vs queues? They seem pretty similar. A producer creates and event/message sent it to a queue/event store and then consumers process the event/message?

  • User profile image
    Elio Damaggio

    @aldo: You should use a property called PartitionKey for your deviceId. What it does is that is hashes all your deviceIds (unlimited number) into your partitions.

    @scyonx: Event Hubs is specifically when your messages are events to be processed (e.g. stored and analyzed) at very high throughput. Event Hubs is not suited when messages represent units of work to be executed (e.g. a workflow) as it does not load balance multiple competing consumers. This means that a worker assigned to an event hub partition will have to process all messages in that partition even if other workers are idle.

  • User profile image

    @Elio Damaggio:Thanks for useful information about PartitionKey for deviceId. Really helps me!

  • User profile image

    Great introduction to event hubs. I'm just wondering why @13:50 when the second receiver is started, it seems to pick up all the partition 0 messages? Shouldn't it coordinate with the 1st receiver so that the 2nd picks up from where the 1st left it? It seems like it's doing this with all other partitions.

Conversation locked

This conversation has been locked by the site admins. No new comments can be made.