Azure Event Grid is a push style distribution of events. Azure Service Buss is a pull-style. Azure Event Hubs is a push-style or pull-style? The sever (Event Hubs) pushes the events to the consumer.? Or the consumer pull the events?
In Kafka we have brokers. We have the leader and the follower. If the leader server goes down, then the follower becomes the leader. Does Azure Event Hubs has something similar?
As I explain in this talk, an Event Hubs deployment, of which we have several hundred, is a 3-tier broker cluster consisting of usually more than 30 VMs spread across 3 availability zones (= independent data centers). If any component across these three tiers goes down, it is instantly replaced in its role by a predesignated secondary (follower). We can lose two entire data centers and your namespace will still be up.
![Blox Fruits Dragon Rework Update [Full Stream]](http://i.ytimg.com/vi/EqDAp8udhm0/mqdefault.jpg)
Azure Event Grid is a push style distribution of events. Azure Service Buss is a pull-style. Azure Event Hubs is a push-style or pull-style? The sever (Event Hubs) pushes the events to the consumer.? Or the consumer pull the events?
The consumer pulls with Event Hubs.
@@clemensv Thanks!
In Kafka we have brokers. We have the leader and the follower. If the leader server goes down, then the follower becomes the leader. Does Azure Event Hubs has something similar?
As I explain in this talk, an Event Hubs deployment, of which we have several hundred, is a 3-tier broker cluster consisting of usually more than 30 VMs spread across 3 availability zones (= independent data centers). If any component across these three tiers goes down, it is instantly replaced in its role by a predesignated secondary (follower). We can lose two entire data centers and your namespace will still be up.
@@clemensv Perfect! Thanks for your answer