Skip to content

Commit daf9ef2

Browse files
committed
event routing
1 parent 95d4d5e commit daf9ef2

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/digital-twins/concepts-events-routing.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: bertvanhoof
77
ms.service: digital-twins
88
services: digital-twins
99
ms.topic: conceptual
10-
ms.date: 09/17/2019
10+
ms.date: 11/07/2019
1111
---
1212

1313
# Routing events and messages
@@ -26,7 +26,9 @@ Users can specify one or more egress endpoints to send out events or to forward
2626

2727
[![Azure Digital Twins events routing](media/concepts/digital-twins-events-routing.png)](media/concepts/digital-twins-events-routing.png#lightbox)
2828

29-
Routing to Event Hubs maintains the order in which telemetry messages are sent. So they arrive at the endpoint in the same sequence as they were originally received. Event Grid and Service Bus don't guarantee that endpoints will receive events in the same order that they occurred. However, the event schema includes a timestamp that can be used to identify the order after the events arrive at the endpoint.
29+
Routing to Event Hubs maintains the order in which telemetry messages are sent. So they arrive at the endpoint in the same sequence as they were originally received.
30+
31+
Event Grid and Service Bus don't guarantee that endpoints will receive events in the same order that they occurred. However, the event schema includes a timestamp that can be used to identify the order after the events arrive at the endpoint.
3032

3133
## Route implementation
3234

0 commit comments

Comments
 (0)