![]() Customers can now leverage the lightweight MQTT protocol to publish and subscribe to messages for telemetry ingestion, client command and control, and broadcast scenarios to build the next generation of applications faster through this fully managed service. This makes Azure Event Grid the first of its kind, MQTT broker in Azure, enabling users to send billions of messages from millions of simultaneously connected devices. Data Generator public preview – This release of the data generator is geared towards early users of Event Hubs and allows users to send user defined or canned events to your Event Hub.Įach of these items are covered in greater depth in their respective announcement blog:Īzure Event Grid now supports bi-directional communication via MQTT version 5 and MQTT version 3.1.1 protocols in Public Preview.Managed Identity for streaming capture – You can use Managed Identity when configuring the storage account to capture your streams.JSON Schema in schema registry for Kafka – The Event Hubs schema registry now supports JSON Schema.Kafka Connect support GA - Use of Kafka Connect is now supported with Azure Event Hubs.This makes it much easier to migrate from your Apache Kafka compatible service to Event Hubs and for you to run hybrid configurations where your source system is Apache Kafka compatible. Mirror Maker 2 support GA – Use of Mirror Maker 2 is now supported with Azure Event Hubs.Compaction GA for Kafka and AMQP – When configured, your Event Hub will only keep the latest message that has the same key.Now at BUILD, Azure Event Hubs has a number of additional changes to announce that make the overall platform even better. This new capability has been well received and provides high performance and low-latency event streaming. To find out more about event streams please see this blog.Įarlier this year, Azure Event Hubs launched their Dedicated self-serve clusters capability to GA. For example, Microsoft Fabric event streams could transform the events into Delta Lake format for the Lakehouse, into SQL columns based on the table schema, or filter events so that homogenous data can be sent to a KQL table. The events could be transformed into the native formats required for the target destination. It enables customers to ingest real-time event data from external event sources into the data stores in Fabric. You can now ingest, capture, transform and route real-time events to various destinations in Microsoft Fabric with a no-code experience using Microsoft Fabric event streams. In this blog we will cover releases from Microsoft Fabric event streams, Azure Event Hubs, Azure Event Grid, and Azure Stream Analytics. ![]() ![]() Azure Messaging and Stream Processing updates will cover recent releases from Azure Messaging and Streaming. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |