1. Building loosely-coupled Apps with Windows Azure Service Bus Topics and Queues Name Title Microsoft Corporation

6. REST Across The Firewall demo

8. Messaging

15. aKite partner

18. Price update in a chain of stores demo

19. Simpler architecture Reduced load on Web Roles and SQL Azure Push-based notification to clients Saved 62% web services calls (15% CPU time) Less infrastructure code required Service Bus handles event notification aKite Retail Web Services focused on business relevant functions aKite scales better!

21. Messaging In Service Bus

22. Hello World! 1 2 3

23. NamespaceManager Management operations on the namespace Create/Delete/Exists for Queues, Topics, and Subscriptions 1 2 3 4

24. MessagingFactory Creates client objects to interact with Queues, Topics, and Subscriptions. Anchor for connection management and multiplexing. 1 2 3 4

25. BrokeredMessage 1 2 3

26. Sending Messages Sending messages is done with Send or Begin/EndSend. You can send on the QueueClient or TopicClient or the neutral MessageSender. 1 2 3

27. Receiving Messages (Destructive) Destructive receives remove the messages from the queue as it is being taken from the broker. Higher throughput than Peek/Lock, but risk of message loss. 1 2

28. Receiving Messages (Peek/Lock) Peek/lock returns messages that have been locked on the queue in the broker. Locked messages are invisible. Complete() deletes them, Abandon() puts them back. 1

31. Managing Topics Management operations on the namespace Create/Delete/Exists for Queues, Topics, and Subscriptions 1 2 3

32. Receiving Messages 1 2

35. Continuous Client with Topics demo

36. A Quick Tour through the SDK Samples demo

37. One more thing…

38. “Iguazu” demo

40. Feedback and questions: http://forums.dev.windows.com http://forums.dev.windows.com Session feedback: http://bldw.in/SessionFeedback

41. Thank You

42. © 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.