ROLE Q/T ROLE Queue/Topic Features: Durable 1:1 – 1:n – Filtered Sessions w/State De-duplication Transactions Batching Scheduling & TTL Auto-forwarding Dead-lettering And Many More…

Download Report

Transcript ROLE Q/T ROLE Queue/Topic Features: Durable 1:1 – 1:n – Filtered Sessions w/State De-duplication Transactions Batching Scheduling & TTL Auto-forwarding Dead-lettering And Many More…

ROLE
1
Q/T
ROLE
2
Queue/Topic Features:
Durable
1:1 – 1:n – Filtered
Sessions w/State
De-duplication
Transactions
Batching
Scheduling & TTL
Auto-forwarding
Dead-lettering
And Many More…
Cloud-Hosted Service
Relay
On-Premises
Resources
Service
DB
User Engagement
Registration at app launch
Client app contacts Platform Notification Service, to
retrieve a “handle” (e.g. ChannelURIs, device tokens)
Client app informs back-end of the “handle”
Client app
Sending notifications
Platform
Notification
Service
App back-end sends a notification to the PNS
PNS pushes the notification to the device/app
Maintenance
App back-end must delete expired handles
App back-end
One-time set up
Create a Notification Hub in Service Bus
It stores the credentials required by the
Platform Notification Service (PNS)
iOS app
Windows Store
app
Register
Client app gets updated handle from PNS
Client app creates (or updates) a registration
on the Notification Hub with current handle
Send Notification
App back-end sends a message to the Hub
Notification Hub pushes message to the PNS
App back-end
APNs
Service Bus
Notification Hub
WNS
Tag:”Beatles”
Tag:”Beatles”
App back-end
Service Bus
Notification Hub
Tag:”Wailers”
<toast>
<visual>
<binding template=\"ToastText01\">
<text id=\"1\">$(message)</text>
</binding>
</visual>
</toast>
App back-end
Hello!
Service Bus
Notification Hub
Hello!
{ message: “Hello!” }
{ aps: { alert: “$(message)” }}
Location Transparency & Addressability
IIS (Node.js) Server 1
Client Group 2
IIS (Node.js) Server 2
Client Group 3
IIS (Node.js) Server 3
Client Group 4
IIS (Node.js) Server 4
Service Bus Topics
Client Group 1
Q1
Q2
Q3
Q4
Q5
Publisher
Q6
Q7
Q8
Q9
S1
S2
S3
S4
S5
Topic
Publisher
S6
S7
S8
S9
All messages
forwarded to all
second tier Topics
S1’
S2’
Topic (distribution layer)
Publisher
S3’
QueueDescription destinationQ = new QueueDescription("myQ2");
QueueDescription sourceQ = new QueueDescription ("myQ1");
sourceQ.ForwardTo = “myQ2";
NamespaceManager nm = NamespaceManager.Create();
nm.CreateQueue(destinationQ);
nm.CreateQueue(sourceQ);
Q1
Q2
Q3
Q4
Q5
Q6
Q7
Q8
Q9
Up to 5 GB
per Queue
S1
S2
S3
S4
S5
S6
S7
S8
S9
Up to 5 GB
for the Topic
Topic
Publisher
Client Platform Diversity
Choosing the Right Auth Model
23a…, n2A…
As1…, aa2…
2E7…, k21
Example rules for a SB Topic, i.e.,
http://myNamespace.servicebus.
windows.net/myTopic
 this bit is the “signature”




false
YvLftH7M
http://channel9.msdn.com/Events/TechEd
www.microsoft.com/learning
http://microsoft.com/technet
http://microsoft.com/msdn