Inspirirani
Section Divider
1-column slide header
Main topic 1
Subtopic 1
Subtopic 2
Main topic 2
Subtopic 1
Subtopic 2
Main topic 3
Subtopic 1
Subtop...
2-column slide header
Main topic 1
Subtopic 1
Subtopic 2
Main topic 2
Subtopic 1
Subtopic 2
Main topic 3
Subtopic 1
Subtop...
Main topic 1
Subtopic 1
2-tile slide header
Main topic 1
Subtopic 1
3-tile slide header
Inspirirani
Ugasite mobitele. Hvala.
Damir Dobric
Lead Architect
DAENET
Connecting
Devices & Services
Internet of Things
AGENDA State of technology &
Devices
Service API Styles
Security
REST or SOAP or more?
How to connect things?
Devices, Things & Co.
Wherewe are today?
IoT Device Taxonomy
Large
Mobile
Micro
Small
Azure M2M
Connection Capability
Large
Mobile
Micro
Small
Azure M2M
Device management
Command & Control
Data Analytics
Inspirirani
Connected devices
1 000 000 000 000 000 000 = 1018
Services: Where we are today?
Web Services
RPC-Api-Style
Resource-API-
Style
Message-API-
Style
Connected System (Point2Point)
ServiceConsumer
Interaction Style
API Style
Security
Trivial Connected System
WebApplication,WebApi
WebServerHTML/JavaScript
Interaction:Request/Response
Style:REST
Security:T...
Trivial Connected System
WCF
WCF ServiceConsumer
Request/Response, Duplex, OneWay,..
RPC
Message/Transport
Request Response
Client Service Interaction
Book Service Design Patterns. Robert Daigneau
Remote Procedure Call (RPC)
API Style
Book Service Design Patterns. Robert Daigneau
var order = proxy.CreateOrder(order);
Resource
API Style
Book Service Design Patterns. Robert Daigneau
sendRequest(“PUT”, http://server/myservice/orders);
None-Trivial Connected System
ThingThing
Interaction Style?
API Style ?
Security?
Thing
Support for HTTP only
No support for WS*
No proxy support
No protocol overhead
Protocol independent
Support WS*
Powerful P...
”Message”API Style!
Book Service Design Patterns. Robert Daigneau
Connecting “things”
Service
This does not work if both
participants are on private
IP.
Bus
Public IP=>
No VPN
Required
Mes...
Broker
Broker
Dependency to:
- Contract
- Broker (Service Bus)
Removed dependency to:
- Protocol
- Service Address
- Runni...
DEMO show
SERVICE BUS
QUEUES
SERVICE BUS
TOPICS & SUBSCRIPTIONS
Windows
(System32)
Windows
RT
Windows
Phone
Service
Bus
Ja...
Consistent Messaging Support
Messaging across platforms
Windows
(System32)
Windows
RT
Windows
Phone
WindowsAzure.Messaging.Managed.dll
WindowsAzure.Ser...
Thank You 
http://developers.de/blogs/damir_dobric/default.aspx
Twitter: /ddobric
https://twitter.com/ddobric
Blog
https:...
Inspirirani
Pitanja i odgovori.
Blog
Twitter: /ddobric
DAENET GmbH
Damir Dobric
daenet GmbH
Microsoft Integration MVP,
Win...
Why Queue?
Load Balancing (Competing Consumer)
• Offline Mode
Broker
Broker
DEMO
SERVICE BUS
TOPICS & SUBSCRIPTIONS
DEMO
SERVICE BUS
TOPICS & SUBSCRIPTIONS
IoT, connecting apps, devices and services
IoT, connecting apps, devices and services
IoT, connecting apps, devices and services
Upcoming SlideShare
Loading in …5
×

IoT, connecting apps, devices and services

662 views

Published on

Shows how to leverage Microsoft Service Bus technology to build the bus for internet of things.

Published in: Software
1 Comment
1 Like
Statistics
Notes
No Downloads
Views
Total views
662
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
18
Comments
1
Likes
1
Embeds 0
No embeds

No notes for slide
  • To provide some perspective on the number of devices consider that today there are 2 Billion PCs on the planet, 5 Billion phones; and 7 Billion people. The forecast is for 50 devices by 2020 and beyond that the forecast is for over 10 trillion individual items with smart technology in them. It’s a staggering number to consider and will drive a change in how we deal with and manage their output. Question for you all: What year was it the number of intelligent connected devices overtook the number of people on the planet: answer 2008
  • IoT, connecting apps, devices and services

    1. 1. Inspirirani Section Divider
    2. 2. 1-column slide header Main topic 1 Subtopic 1 Subtopic 2 Main topic 2 Subtopic 1 Subtopic 2 Main topic 3 Subtopic 1 Subtopic 2
    3. 3. 2-column slide header Main topic 1 Subtopic 1 Subtopic 2 Main topic 2 Subtopic 1 Subtopic 2 Main topic 3 Subtopic 1 Subtopic 2 Main topic 1 Subtopic 1 Subtopic 2 Main topic 2 Subtopic 1 Subtopic 2 Main topic 3 Subtopic 1 Subtopic 2
    4. 4. Main topic 1 Subtopic 1 2-tile slide header
    5. 5. Main topic 1 Subtopic 1 3-tile slide header
    6. 6. Inspirirani Ugasite mobitele. Hvala.
    7. 7. Damir Dobric Lead Architect DAENET Connecting Devices & Services Internet of Things
    8. 8. AGENDA State of technology & Devices Service API Styles Security REST or SOAP or more? How to connect things?
    9. 9. Devices, Things & Co. Wherewe are today?
    10. 10. IoT Device Taxonomy Large Mobile Micro Small Azure M2M
    11. 11. Connection Capability Large Mobile Micro Small Azure M2M Device management Command & Control Data Analytics
    12. 12. Inspirirani Connected devices 1 000 000 000 000 000 000 = 1018
    13. 13. Services: Where we are today? Web Services RPC-Api-Style Resource-API- Style Message-API- Style
    14. 14. Connected System (Point2Point) ServiceConsumer Interaction Style API Style Security
    15. 15. Trivial Connected System WebApplication,WebApi WebServerHTML/JavaScript Interaction:Request/Response Style:REST Security:Transport
    16. 16. Trivial Connected System WCF WCF ServiceConsumer Request/Response, Duplex, OneWay,.. RPC Message/Transport
    17. 17. Request Response Client Service Interaction Book Service Design Patterns. Robert Daigneau
    18. 18. Remote Procedure Call (RPC) API Style Book Service Design Patterns. Robert Daigneau var order = proxy.CreateOrder(order);
    19. 19. Resource API Style Book Service Design Patterns. Robert Daigneau sendRequest(“PUT”, http://server/myservice/orders);
    20. 20. None-Trivial Connected System ThingThing Interaction Style? API Style ? Security? Thing
    21. 21. Support for HTTP only No support for WS* No proxy support No protocol overhead Protocol independent Support WS* Powerful Proxy tooling Protocol overhead REST or SOAP ?  Two different approaches (apple or pear ?)  Compete only in very simple scenarios.  SOAP: Better for enterprises and services based on standards, policies and governance.  REST: Better (mostly) for web. Very simple and suitable for broad set of devices. SOAP (RPC) REST (Resource)
    22. 22. ”Message”API Style! Book Service Design Patterns. Robert Daigneau
    23. 23. Connecting “things” Service This does not work if both participants are on private IP. Bus Public IP=> No VPN Required Message is received as pull. All participants are behind firewall Can use Relay, Queue or Topic Participants can support different protocols: HTTP, SBMP, AMQP NO VPN required!!
    24. 24. Broker Broker Dependency to: - Contract - Broker (Service Bus) Removed dependency to: - Protocol - Service Address - Running state (offline)
    25. 25. DEMO show SERVICE BUS QUEUES SERVICE BUS TOPICS & SUBSCRIPTIONS Windows (System32) Windows RT Windows Phone Service Bus Java Script
    26. 26. Consistent Messaging Support
    27. 27. Messaging across platforms Windows (System32) Windows RT Windows Phone WindowsAzure.Messaging.Managed.dll WindowsAzure.ServiceBus.dll WindowsAzure.Messaging.Managed.dll Service Bus Node JS var azure = require('azure'); Java Script ServiceBus JavaScript SDK
    28. 28. Thank You  http://developers.de/blogs/damir_dobric/default.aspx Twitter: /ddobric https://twitter.com/ddobric Blog https://daenet.de DAENET GmbH Damir Dobric daenet GmbH Microsoft Integration MVP, Windows Azure VTSP damir.dobric@daenet.com
    29. 29. Inspirirani Pitanja i odgovori. Blog Twitter: /ddobric DAENET GmbH Damir Dobric daenet GmbH Microsoft Integration MVP, Windows Azure VTSP damir.dobric@daenet.com
    30. 30. Why Queue? Load Balancing (Competing Consumer) • Offline Mode Broker Broker
    31. 31. DEMO SERVICE BUS TOPICS & SUBSCRIPTIONS
    32. 32. DEMO SERVICE BUS TOPICS & SUBSCRIPTIONS

    ×