Please enable JavaScript.
Coggle requires JavaScript to display documents.
2.4 azure event hubs - Coggle Diagram
2.4 azure event hubs
What is
- cloud-based, event-processing service
- can receive and process millions of events per second
event pipeline,
receive incoming data and stores this data until processing resources are available.
- entity that sends data to the Event Hubs is called a publisher,
- and an entity that reads data from the Event Hubs is called a consumer or a subscriber
- Azure Event Hubs sits between these two entities
Pricing
Basic, Standard, and Dedicated
- You can't change the throughput unit once you set it.
- different Event Hubs for different throughput requirements
requirements
configure an application to send messages to an Event Hub
- Event Hub namespace name
- Event Hub name
- Shared access policy name
- Primary shared access key
configure an application to receive messages from an Event Hub
- Event Hub namespace name
- Event Hub name
- Shared access policy name
- Primary shared access key
- Storage account name
- Storage account connection string
- Storage account container name
publish
- HTTPS
- Advanced Message Queuing Protocol (AMQP) 1.0.
better performances but higher initial session overhead
Event subscribers
two supported programmatic methods to receive and process events from an Event Hub.
- EventHubReceiver - A simple method that provides limited management options.
- EventProcessorHost - An efficient method that we'll use later in this module.
Consumer groups
specific view of an Event Hub data stream
- multiple subscriber applications can process an event stream independently
options
- Enable Kafka.
- namespace zone redundant
- Enable Auto-Inflate and Auto-Inflate Maximum Throughput Units
automatic scale-up option by increasing the number of throughput units up to a maximum value
performance
- Throttled Requests: The number of throttled requests because the throughput exceeded unit usage.
- ActiveConnections
- Incoming/Outgoing Bytes