Yaler  – a simple, open and scalable relay infrastructure WoT 2010 Oberon microsystems Thomas (tamberg@oberon.ch)
HTTP/1.1
Enable  monitoring and remote control from any Web browser https://...
…  of thousands *  of embedded devices.             *) Customer requirement: 500’000; work in progress https://...
Ideally  that just works. https://...
But  in reality, the challenges are…
Accessibility
Addressability https://???.???.??.??
Yaler  is a simple relay infrastructure based on Linden Lab’s Reverse HTTP.
Devices are  published  with HTTP/1.1 POST  /device-id Upgrade: PTTH/1.0 Connection: Upgrade Host: yaler.net
…  and  accessed  with HTTP/1.1 GET  /device-id/resource Host: yaler.net
Yaler  reverses  the connection HTTP/1.1  101 Switching Protocols Upgrade: PTTH/1.0 Connection: Upgrade
…  and  forwards  the  request . GET  /device-id/resource Host: yaler.net
The device  responds  with HTTP/1.1 HTTP/1.1  200  OK { "feed": [ { "entry": ...
Yaler  returns  the  response HTTP/1.1  200  OK { "feed": [ { "entry": ...
But  this poses two new challenges…
Scalability
Availability
Yaler is  engineered  for high performance, maintainability,  robustness.
Yaler is  implemented  with Java’s non-blocking sockets, hierarchical state machines,  and Design by Contract.
Scalability  and  availability  can be achieved by coordinating relays with consistent hashing and a group membership serv...
Yaler  is available as open source software at  http://yaler.org/
This presentation is online at  http://goo.gl/4uaD                 Thanks  for your time.
Upcoming SlideShare
Loading in …5
×

Yaler WoT V20100325b

1,369 views

Published on

WoT 2010 presentation. For more info see http://www.webofthings.com/wot/2010/ and http://yaler.org/

Published in: Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,369
On SlideShare
0
From Embeds
0
Number of Embeds
571
Actions
Shares
0
Downloads
14
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Yaler WoT V20100325b

  1. 1. Yaler – a simple, open and scalable relay infrastructure WoT 2010 Oberon microsystems Thomas (tamberg@oberon.ch)
  2. 2. HTTP/1.1
  3. 3. Enable monitoring and remote control from any Web browser https://...
  4. 4. … of thousands * of embedded devices.             *) Customer requirement: 500’000; work in progress https://...
  5. 5. Ideally that just works. https://...
  6. 6. But in reality, the challenges are…
  7. 7. Accessibility
  8. 8. Addressability https://???.???.??.??
  9. 9. Yaler is a simple relay infrastructure based on Linden Lab’s Reverse HTTP.
  10. 10. Devices are published with HTTP/1.1 POST /device-id Upgrade: PTTH/1.0 Connection: Upgrade Host: yaler.net
  11. 11. … and accessed with HTTP/1.1 GET /device-id/resource Host: yaler.net
  12. 12. Yaler reverses the connection HTTP/1.1 101 Switching Protocols Upgrade: PTTH/1.0 Connection: Upgrade
  13. 13. … and forwards the request . GET /device-id/resource Host: yaler.net
  14. 14. The device responds with HTTP/1.1 HTTP/1.1 200 OK { "feed": [ { "entry": ...
  15. 15. Yaler returns the response HTTP/1.1 200 OK { "feed": [ { "entry": ...
  16. 16. But this poses two new challenges…
  17. 17. Scalability
  18. 18. Availability
  19. 19. Yaler is engineered for high performance, maintainability, robustness.
  20. 20. Yaler is implemented with Java’s non-blocking sockets, hierarchical state machines, and Design by Contract.
  21. 21. Scalability and availability can be achieved by coordinating relays with consistent hashing and a group membership service (work in progress)
  22. 22. Yaler is available as open source software at http://yaler.org/
  23. 23. This presentation is online at http://goo.gl/4uaD                 Thanks for your time.

×