Real Life WebSocket Case Studies and Demos

transcript

Real Life WebSocket Case Studies & Demos

Todays’ Featured Speakers: Chuck Liddell Technology Architect Pythio Dave Combs Development Engineer Kaazing Peter Moskovits Developer Evangelist Kaazing

Tuesday, March 27, 2012 9 AM PT 12 PM ET 5 PM GMT

Phone conference dial-‐in details:

1.  VoIP or select Use Telephone aJer joining the webinar

2.  United States: 773-‐945-‐1012 Access Code: 268-‐876-‐074 Audio PIN: Shown aJer joining the webinar

(Other countries: check confirmaWon email for dial-‐in number) Webinar ID: 679-‐283-‐998

A Li[le Housekeeping

•  Join the audio with the “Use Mic & Speakers” op3on (VoIP)

•  Or join the conference by selec3ng “Use Telephone” and dial the number

•  Your line will remain muted

•  Submit your text ques3on using the Ques3ons pane

How to parWcipate today

Pythio Technology Platform Chuck Liddell, Technology Architect

What do we do?

"  Pythio Ltd offers a product line of GSM-based telemetry, monitoring & remote management, and fully integrated microcontroller-based solutions.

"  We deliver a sophisticated and comprehensive remote management experience that abstracts the hardware and software complexities and provides you with an intuitive interface.

Legacy Architecture

Device Device Server Database User

PHP Web

Server

Real-time

Redesign Goal

Develop an end-to-end technology architecture that satisfies the following criteria:

"  Provide flexible telemetry with bidirectional communications" for remote devices

"  Give users comprehensive access to specific devices and" aggregated data / statistics

"  Link all components in real-time environment

"  Provide clear, modular path for expansion

"  Scale gracefully

New Architecture

Device Universal Server

Database

User Kaazing

Web Gateway

Real-time

Results

"   Real-time system allows system components to monitor and act on a huge variety of message types and sources.

"   Reduction in server load: several HTTP requests per client per second became zero, as clients now simply register for server messages and wait.

"   Reduced latency: legacy system “real-time” streaming had a 3-5 second delay, new design delay is only 400-500 ms end-to-end from device to server to user.

Contact Info

"   chuck@pythio.com "   http://pythio.com

High Performance

Shrink-‐Wrapped Complexity

Enterprise Support

Web. Upgraded.

Ultramarathon Real-‐Wme Publishing of

Running Events to the Web

Dave Combs Kaazing Development Engineer

March 27, 2012

IntroducWon

•  Dave Combs

•  Member of Kaazing Development team (Tools Group)

•  Ultrarunning par3cipant (25 years) •  Programmer for almost 40 years

Ultrarunning

§  Longer than 26.2 miles (42,195 km)

§  Trails, roads, tracks §  Distance Events

•  50 km, 50 miles, 100 km, 100 miles, ... (3100 miles!!)

§  Timed Events •  6, 12 hours •  1, 2, 3, 6 days

Ultrarunning Video

Why Ultrarunning Online?

§  Timing computers became available §  Lots of data available (aid sta3on or lap 3mes) §  Ultrarunners (runners in general) love sta3s3cs!

§  Virtual par3cipa3on -‐ events take hours or days, family & friends like to "watch" the events unfold

Why Ultrarunning Using WebSockets?

Example: Across The Years -‐ 24, 48, 72 Hours over New Years (125-‐250 par3cipants, ~200 "watchers" online) §  Manual FTP text file to website every 2-‐3 hours §  Programma3c FTP HTML page every hour §  Programma3c connec3on to 3ming computer, upload latest data every 12 seconds

§  WebSocket upload immediately to website and browser

Architecture

Timing System

Architecture

Timing System

Architecture

Timing System

Architecture Details

①  Java program at race site •  Connects to 3ming data source ("real world") •  Connects to WebSocket Gateway as Java client •  "Source of truth" for race data to the web

②  WebSocket gateway •  In the cloud (easily accessible to viewers) •  Local database for race data storage •  Supports publish/subscribe API (JMS) •  Only one port needed to access/store data

③  End-‐user browser •  Any browser back to IE6 •  Connects to KWG as JavaScript client •  Page built with JavaScript, JQuery, PHP

①  ②  ③ 

Issues to address to build this

§  Message types and connec3ons •  Pub/sub (above raw websockets) -‐ MUCH easier to program

§  Connec3vity loss •  Source of truth at site, backup online, auto-‐reconnect with Kaazing client technology

§  Performance •  Ini3ally only "metadata" (events, runners)

•  Subsequently only 3ming data (very small message)

•  Gateway can scale easily •  Client is an applica3on, not just a page

Thank you!

Thank you for parWcipaWng today

Time for Q&A

•  Submit your text questions now using the webinar Questions pane

•  For additional information contact us at info@kaazing.com

•  Note: A link to an archive recording of this webinar will be emailed to you within 48 hours of the conclusion of this event.

Panelists Chuck Liddell Technology Architect, Pythio chuck@pythio.com Dave Combs Developer Engineer, Kaazing dave.combs@kaazing.com Peter Moskovits Developer Evangelist, Kaazing peter.moskovits@kaazing.com

AddiWonal InformaWon

You will receive a follow-‐up email with a link to the recording of the event within 48 hours For more informa3on, please contact info@kaazing.com