Contenu connexe Similaire à Real Life WebSocket Case Studies and Demos Similaire à Real Life WebSocket Case Studies and Demos (20) Plus de Peter Moskovits (9) 1. Real
Life
WebSocket
Case
Studies
&
Demos
Tuesday,
March
27,
2012
9
AM
PT
12
PM
ET
5
PM
GMT
Todays’
Featured
Speakers:
Phone
conference
dial-‐in
details:
Chuck
Liddell
1. VoIP
or
select
Use
Telephone
aJer
joining
Technology
Architect
the
webinar
Pythio
2. United
States:
773-‐945-‐1012
Access
Code:
268-‐876-‐074
Dave
Combs
Audio
PIN:
Shown
aJer
joining
the
webinar
Development
Engineer
(Other
countries:
check
confirmaWon
email
for
Kaazing
dial-‐in
number)
Peter
Moskovits
Webinar
ID:
679-‐283-‐998
Developer
Evangelist
Kaazing
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
2. A
Li[le
Housekeeping
How
to
parWcipate
today
• 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
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
4. 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.
7. 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
9. 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.
11. Ultramarathon
Real-‐Wme
Publishing
of
Running
Events
to
the
Web
Shrink-‐Wrapped
Complexity
Web.
Upgraded.
High
Performance
Enterprise
Support
Dave
Combs
Kaazing
Development
Engineer
March
27,
2012
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
12. IntroducWon
• Dave
Combs
• Member
of
Kaazing
Development
team
(Tools
Group)
• Ultrarunning
par3cipant
(25
years)
• Programmer
for
almost
40
years
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
13. 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
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
15. 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
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
16. 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
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
19. Architecture
Timing
System
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
20. Architecture
Timing
System
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
21. Architecture
Timing
System
Web
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
22. 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
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
23. 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
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
24. Thank
you!
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
25. 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.
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
26. Q
&
A
Panelists
Chuck
Liddell
Technology
AarWcipate
tPythio
How
to
p rchitect,
oday
chuck@pythio.com
Dave
Combs
Developer
Engineer,
Kaazing
dave.combs@kaazing.com
Peter
Moskovits
Developer
Evangelist,
Kaazing
peter.moskovits@kaazing.com
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
27. AddiWonal
InformaWon
You
will
receive
a
follow-‐up
email
with
a
link
to
the
recording
oarWcipate
today
within
48
hours
How
to
p
f
the
event
For
more
informa3on,
please
contact
info@kaazing.com
Copyright
©
2012
Kaazing
Corpora3on.
All
Rights
Reserved.
