Microsoft Data Platform weekly update can be your solution. It’s a weekly update on the topics related to Latest data Platform updates empowered by Microsoft Azure platform to deliver value to the business.
If you want to receive these updates weekly, then don’t forget to follow my blog!
Microsoft Announcement & Updates by Product
IOT Hub device telemetry events in Event Grid – Public Preview
Event Grid is a fully managed event service that enables you to easily manage events across many different Azure services and applications. Made for performance and scale, it simplifies building event-driven applications and serverless architectures. Learn more about Azure Event Grid.
One of the most awaited feature since launch the Azure IoT Hub integration with Event Grid is device telemetry events. Now the feature is enabled and is in public preview.The new capability to subscribe to device telemetry events, allows you to easily integrate data from your devices into other Azure services, including serverless compute services like Azure Functions and Azure Logic Apps as well as non-Azure services using webhooks. This helps simplify IoT architectures by eliminating the need for additional services that poll for device telemetry for further processing. For more information read here.
- Events up to 1MB in Event Grid – public preview
Event Grid now supports events of up to 1MB in size. There are no configuration changes required, and this will work on existing event subscriptions. To try it out, just push larger events. Everything under 64 KB will be still be covered by our GA SLA.
The batch size limit for events sent to Event Grid as a JSON array is still 1MB. Events over 64 KB will be charged in 64 KB increment (e.g. an event of 100 KB will be charged as though it is two separate events). Read more here.
2. Event Grid can now publish events to Service Bus.
Including Service Bus as an event handler for Event Grid in public preview, being able to receive events for further processing. Service Bus can now act as either an event source or event handler, making for a more robust experience delivering events and messages in distributed enterprise applications.
Event Grid can now publish events directly to Service Bus queues in any tier. This feature is currently in public preview and does not work with Service Bus Topics and Sessions.
Try it out via portal, CLI, or PowerShell by setting the endpoint type to Service Bus, and selecting the Service Bus queue you’d like to publish to. For more information read here.
3. Geo Disaster Recovery now available in event grid.
Event Grid now has built-in automatic geo disaster recovery (GeoDR) of metadata, applicable to all existing Domains, Topics and Event Subscriptions, not just for new ones. This means that, in the event of an outage that takes out an entire Azure region, the Event Grid service will already have all of your eventing infrastructure metadata synced to a paired region and your new events will begin to flow again with no intervention required, avoiding service interruption.
Disaster recovery is generally measured with two metrics:
- Recovery Point Objective (RPO): the minutes or hours of data that may be lost.
- Recovery Time Objective (RTO): the minutes of hours the service may be down.
Event Grid’s automatic failover has different RPO’s and RTO’s for your metadata (event subscriptions, etc.) and data (events). If you need different specification from below, you can still always implement your own client-side failover using the topic health APIs.
- Metadata RPO: Zero minutes. You read that right. Any time a resource is created in Event Grid, it’s instantly replicated across regions. In the event of a failover, no metadata is lost.
- Metadata RTO: Although generally this happens much more quickly, within 60 minutes, Event Grid will begin to accept create/update/delete calls for topics and subscriptions.
- Data RPO: If your system is healthy and caught up on existing traffic at the time of regional failover, the RPO for events is about 5 minutes.
Data RTO: Like metadata, this generally happens much more quickly, however within 60 minutes Event Grid will begin accepting new traffic after a regional failover. For More Information Read here.
4. Event Domains Generally available in Event Grid.
Event Domains is now available for use in production scenarios. This feature on Azure Event Grid allows you to centralize the events delivery management for multi-tenant applications (for example, a SaaS solution), having hundreds of thousands of topics in a single domain with a single publish endpoint. This way, instead of sending the events of a solution individually to each of its end customers, you can send all the events to the domain and Event Grid will handle the routing and delivery. Each topic can have fine grain authorization permissions set on a per-tenant basis, controlled by Azure Active Directory, making sure the right events are delivered to the right customer.
Event Domains limits with general availability includes:
- 100,000 topics per event domain*
- 100 event domains per Azure subscription*
- 500 event subscriptions per topic in an event domain
- 50 ‘firehose’ event subscriptions at the event domain scope
- 5,000 events/second into an event domain*
For More Information Read here.