►
From YouTube: KEYNOTE: Evolve or Fall Behind - A Digital Revolution Powered by Node.js by Andy Hoyt, IBM
Description
KEYNOTE: Evolve or Fall Behind - A Digital Revolution Powered by Node.js- Andy Hoyt, IBM
We are in the midst of the Information Age where businesses are rapidly transforming themselves to fit the needs of increasingly digital society. In all economic sectors, we are seeing that businesses must evolve or get left behind. Node.js is the keystone for facilitating this evolution, enabling companies to greatly increase developer productivity, spend less time on infrastructure and have peace-of-mind with long-term support. Learn how Node.js is proving to be the forefront of digital transformation, from fueling the growth of the API economy to revolutionizing infrastructure with serverless applications.
About Andy Hoyt
Andrew Hoyt is the Director of API Connect, DataPower, and Strongloop Development as part of the Interaction Services organization in the IBM Cloud Unit. Interaction Services is a new tier of services emerging at the edge of the enterprise. This tier is being driven by the transformation into the digital era. Developers are composing – writing code, connect to pipelines of data and integrating APIs for use within new systems of engagement. These APIs are backed by microservices that require capabilities to CREATE, DEPLOY, MANAGE and ENFORCE the availability of these services. Andrew owns the development and client engineering of these capabilities for IBM.
Andrew is a graduate of Marist College in Poughkeepsie NY, USA. Andrew has spent 15 years in IBM Software Group specializing in areas such as WebSphere, z/OS, PureApplication, and Cloud development.
A
Good
morning,
I
know
I'm
real
excited
to
be
here,
especially
where
I
get
to
talk
about
some
of
my
favorite
topics,
which
is
node
and
api's,
and
how
that's
really
powering
the
digital
world
that
we
live
in
today
and
the
world
right.
As
we
all
know,
it
is
changing
by
the
second,
it's
constantly
evolving
and
that's
all
powered
through
technology,
advancements
that
are
happening
out
there
and
we,
as
end-users,
are
only
adding
to
the
fire.
We
want
it.
We
want
more,
we
want
it
easier
and
we
want
it
faster
so
to
provide
that
I'm.
A
Just
gonna
do
a
quick
example
right
and
imagine
that
was
something
that
we
all
do
on
a
regular
basis
going
out
to
a
new
restaurant
for
dinner.
So
my
wife
and
I
live
in
a
rural
area
and
we're
going
to
a
new
restaurant
downtown,
so
simple
questions:
how
do
I
get
there?
What
am
I
going
to
order
and
where
to
park?
Simple
things,
I
think
they
apply
to
a
lot
of
different
scenarios
as
well.
A
So
with
that
the
API
economy
in
the
world
today
and
in
our
daily
life,
they
provide
us
a
number
of
different
things
that
help
us
with
that
the
GPS
within
our
car
or
our
cell
phones.
That
help
us
get
from
point
A
to
point
B.
Well,
I
can
figure
out
how
to
get
to
that
restaurant.
That
first
question
solved.
I
can
go
ahead
and
look
at
the
websites
menu
and
understand
what
I
might
want
to
order
in
ahead
of
time
or
I
can
go.
A
Look
at
things
like
Yelp
that
provide
that
information,
but
I
feel
like
there's,
always
there's
something
more
that
we
can
need
that
can
help
better.
That
overall
experience
that
we
have
so
imagine
what,
if
the
restaurant
exposed
their
menu
by
an
API
and
the
application
code,
would
actually
be
able
to
pre-order
the
appetizer
for
you
and
have
it
arrive
when
I
got
there
based
off
of
the
GPS
of
my
car.
So
at
times
they're
perfectly
when
I
arrive.
A
What
if
the
automaker
integrated
with
this
home
security
API,
where
you
could
turn
on
the
security
cameras
this
the
minute
you
left
the
garage
and
what
the
TV
providers
exposed
a
programming
guide
API,
so
that
the
application
can
record
the
basketball
game
or
whatever
you
want,
as
the
user
won't
be
in
home
and
time
based
on
the
geolocation
of
the
car
right
and
the
possibilities
are
really
endless
around
those
types
of
scenarios
and
to
really
capture
the
benefits
of
the
API
economy.
There's
a
number
of
different
things
that
it
affects.
A
The
first
is
the
delightful
experience.
Well
for
me,
as
the
end
user,
well,
I
had
a
wonderful
experience.
My
meal
was
better
I
got
the
appetizer
waiting
for
me
and
that
over
that
that
felt
real
good
I
was
eight,
not
able
I
didn't
have
to
drive
around
for
10
minutes
with
in
my
car,
looking
for
a
spot
in
a
crowded
traffic
area,
I
didn't
and
maybe
not
even
10,
minutes
walking
from
that
parking
spot
to
the
restaurant
itself.
I
felt
safer
with
my
kids
at
home,
because
the
moment
I
exited
the
garage.
A
Well,
my
security
cameras
came
on
and
I
didn't
have
to
worry
about
forgetting
or
if
things
were
not
locked
up
in
a
proper
way
and
finally
right,
we
didn't
have
to
rush
home
to
turn
on
that
Knicks
game.
Well,
maybe
that's
a
good
thing,
because
if
you
guys
like
the
Knicks
they
stink-
and
you
know
they
don't
have
to
worry
about
that
and
I
could
watch
the
game
not
get
in
trouble
with
my
wife
and
you
know,
I've
got
it
recorded
for
a
later
time.
A
So
all
things
that
then
made
my
life
a
lot
better
by
all
of
that
by
different
api's
being
exposed
so
that
applications
then
could
take
advantage
of
it.
I
mean
there
are
other
aspects
as
well.
We
think
about
direct
revenue
for
the
restaurant
itself.
Well,
they
have
more
appetizers
being
bought
so
more
money,
good
recommendations
from
the
the
end
users,
because
of
the
satisfaction
that
they
had
so
more
folks
coming
and
return
users
as
well
and
certainly
pot.
You
know
parking,
the
city
gets
the
additional
revenue
as
well.
A
You
know
more
parking,
lots
or
fully
fully
utilized
left
traffic
on
the
streets
for
parking,
less
clogged,
so
making
overall
downtown
a
better
experience
and
obviously
there's
a
lot
of
indirect
revenue
as
well
with
things
around
Google
and
nest
and
BMW
I
ftt
and
others
where
they
can
take
advantage
of
all
of
the
different
API
is
being
exposed
for
applications
that
they
build.
Another
quick
example
is
really
around.
You
know
a
number
of
different
things.
One
is
Starbucks.
A
If
we
think
about
what
they've
done
right
going
fully
digital
having
a
huge
payments
business,
it's
really
transforming
the
way.
We
do
things
just
you
know.
A
few
weeks
ago,
I
woke
up.
I
was
out
of
coffee
in
my
house,
so
hey,
not
a
problem.
There
there's
a
number
of
different
coffee
stores
on
my
way
to
wait
it
to
the
office.
Now,
there's
three
all
in
one
particular
area
and
I
chose
Starbucks
for
a
very
simple
reason,
not
because
the
coffee
was
better
because
it
is
actually
my
least
favorite
of
the
three.
A
But
the
digital
experience
that
I
had
was
so
much
better.
I
was
able
to
order,
and
by
and
pick
it
up
in
such
a
short,
easy
time
compared
to
the
others
that
have
made
the
decision
really
easy
for
us
to
do
and
all
based
off
of
that
digital
experience.
You
know,
there's
a
special
car
company,
that's
doing
sending
connected
car
data
out
to
insurance,
vendors
and
others
so
that
they
can
insurance
vendors
can
take
advantage
of.
A
A
Being
able
to
handle
the
dynamics
and
the
challenges
that
API
is
present,
your
business
needs
to
be
able
to
handle
millions
of
users
billions
of
devices
that
are
out
there
today
and
if
you're
api's
can't
handle
that
you're
not
really
transforming
your
company,
your
business
in
itself,
if
that
API,
that
didn't
have
that
I
wanted
to
order
that
appetizer
on
couldn't
scale
well,
my
experience
is
actually
a
lot
worse
than
it
ever
was
before
him.
You
know
typical
monolithic
applications
are
slow
and
not
able
to
handle
the
dynamic
needs
that
are
out
there
today.
A
And
finally,
you
know
how
do
you,
how
do
you
handle
the
lifecycle
of
your
api's
from
the
creation
of
it
to
the
management
to
the
security
to
the
retirement
of
the
api's?
All
of
these
things
are
leading
us
towards
a
shift
in
the
programming
model,
and
that
shift
is
absolutely
node
in
itself,
and
node
has
really
emerged
as
the
standard
for
api's
and
micro
services
really
really
allowing
the
businesses
to
scale
to
unprecedented
and
client
request.
A
Now
my
team
I'll
say
is
a
perfect
example
that,
with
our
development
of
some
of
the
offerings
that
we
have,
we
had
a
monolithic
application.
We've
been
breaking
it
down
into
smaller
micro
services
based
off
of
node,
and
we
have
seen
greater
scale,
whether
it
be
for
our
on-premises
clients
or
even
in
our
more
poorly
in
our
cloud
and
even
more
importantly,
we've
gotten
so
much
more
efficient.
We're
writing
more
code,
better
code
by
leveraging
node
as
the
platform
for
our
architecture.
A
So
what
this?
What
that
does
is?
It
leads
us
to
this
new
architecture
right
and
we've
all
seen,
write
the
top
and
understand.
We've
got
the
systems
of
engagement
with
the
web,
mobile
and
IOT
all
way
to
the
bottom,
with
our
systems
of
record
and
the
data
that
opposed
s's
and
you're
in
right,
above
that,
your
traditional
SOA
architecture.
A
You
know
fueling
the
connectivity
to
that
data,
but
there
is
that
new
architecture
that
is
needed,
that
in
an
interaction
services,
layer
that
is
going
to
handle
out
the
scale
and
the
micro
services
that
you
need
to
do
to
handle
the
new
digital
world
that
we
live
in
today
and
what
is
needed
right.
It's
really
designed
for
that
micro
services
architecture,
as
I
mentioned
right,
non-blocking,
event-driven
IO
to
remain
lightweight,
support,
massive
concurrency
and
be
able
to
provide
the
ability
to
have
a
simplified
and
comprehensive
API
lifecycle
to
create
manage
secure
your
api's.
A
A
You
know,
wanna
be
able
to
have
abstract
developers
from
the
infrastructure
in
itself
right
all
of
these
types
of
things,
and
these
are
just
some
of
those
requirements
that
are
leading
us
to
what
we
see
around
serverless
technology
and
what
service
computing
frameworks
right
when
triggered
by
an
external
event.
It
invokes
autonomous
code
snippets
right
and
these
snippets
are
loosely
coupled
with
each
other
that
are
essentially
designed
to
perform
one
task.
At
a
time
now,
within
IBM
we've,
we
started
an
open
project
with
open
wisk.
A
So
with
that,
if
we
think
about,
then
you
know
this
integration
services,
architecture
in
itself
and
we
have
node
and
we've
got
open
wisk
or
any
of
the
service
platforms.
You
know
it's
a
perfect
marriage
with
the
two
of
them
together
right.
It's
the
ideal
length
note
is
absolutely
the
ideal
language
for
our
service
environments.
It's
lightweight,
it
starts
up
quickly
and
it's
great
for
I/o,
so
I
can
keep
talking
about
it.
B
For
the
introduction,
Andy
I'm
really
excited
to
show
you
guys
my
demo
today.
What
we've
got
here
is
a
slack
application,
sure
everyone's
familiar
with
slack,
pretty
popular
team
collaboration
tool.
Slack
apps
are
these
bots
that
send
automated
messages.
What
I've
got
here
is
a
slack
app
that
I
want
to
show
you
guys
kind
of
just
to
set
the
scenario.
Let's
imagine
we
have
a
customer
feedback
channel
whenever
a
customer
posts
feedback
on
one
of
our
products,
it'll
automatically
get
posted
into
this
channel.
B
B
Let's
take
a
look
at
what
happens
when
some
sample
negative
feedback
gets
posted
and
I
just
pulled
these
off
of
a
Amazon
review
in
a
few
seconds.
Okay,
we
get
a
response
back
and
it
says
it's
a
high
severity
feedback.
It's
detected
there's
a
high
sense
of
sadness
in
this
message
and
even
some
anger
seems
to
make
sense.
Let's
see
some
sample
positive
feedback,
okay,
hoping
it'll,
come
back
with
low
severity
demo
gods,
don't
fail
me
now,
I.
B
Actually
can
make
it
any
bigger.
Oh
there
we
go
there,
we
go
it's
working,
we'll
give
it
one
more
shot.
Oh
there
you
go,
it
came
back
so
based
on
that
tonal
analysis.
It
gave
it
a
low
severity.
It
detected
that
the
strongest
tone
was
joy,
I
sense,
some
anger,
but
it's
not
very
confident
about
it.
So,
okay,
hopefully
our
customer
engagement
team
is
more
equipped
to
respond
to
this
feedback.
Now
that
they've
got
a
severity
assigned
to
it,
let's
take
a
look
at
how
these
how
the
slack
app
was
actually
created.
B
B
Remember
this
URL
we'll
come
back
to
it
in
a
minute.
That's
all
I
want
to
talk
about
the
slack
API
side.
For
now,
let's
switch
to
open
wisk
andy
quickly,
introduced
open
wisk,
it's
basically
an
open
source
server
list
computing
platform
sounds
a
little
bit
complicated,
but
very
basically,
I
can
host
some
scripts
on
this
platform
and
whenever
an
API
is
called
that
node.js
runtimes
brought
up,
the
script
is
run,
does
what
it
needs
to
and
then
brings
itself
all
back
down.
B
Let's
take
a
look
at
how
easy
it
is
to
get
started
with
open,
Wisc
I'll
jump
into
the
develop
you
and
I'll
create
an
action.
I'll
call
it
sample.
Interactive
will
choose
note
6,
as
the
execution
of
runtime.
We've
also
got
no.12,
Python,
swift
and
we'll
start
with
the
hello
world
sample
that
lets
me
choose
just
a
quick
note.
Nodejs
is
perfect
for
service
applications,
it's
lightweight,
so
it
starts
so
quickly.
It's
asynchronous
by
nature,
which
is
perfect
for
things
like
our
slack
bot
and
makes
managing
and
calling
api
super
easy.
B
B
Just
need
to
change
one
thing:
the
JSON
that's
getting
passed
in
so
I'll
change
it
to
message
and
hello
from
node,
interactive;
okay,
that's
that
was
really
fast
actually,
so
it
called
the
open,
whisk
action
which
responded
successfully
with
the
message
you
sent
me
hello
from
node
interactive
and
there
we
go.
We
just
created
our
first
action
on
a
server
this
platform,
jumping
back
I'm
gonna
delete
that
action.
I
just
created
I,
already
got
three
actions
configured
here.
For
the
sake
of
time,
these
are
the
ones
that
my
slack
bot
uses.
B
So
this
is
what
actually
goes
to
Watson,
actually
to
do
the
tonal
analysis
of
the
message
being
posted,
so
we've
got
two
big
pieces
of
the
puzzle.
Here
we've
got
slack,
which
reads
the
messages
being
posted
in
this
channel
and
calls
some
API
and
we've
got
open
wisk,
which
is
expecting
to
receive
that
API
and
and
run
some
smart
API
calls
and
that
kind
of
thing.
B
What
we
need
here
is
an
API
gateway
in
between
and
what
that'll
do
is
essentially
massage
the
data
coming
from
slack
into
a
format
that
opened
wispy
steps
and
it's
gonna,
add
the
right,
authentication,
headers
and
that
kind
of
thing
open,
which
gives
us
a
really
cool
command.
That
makes
it
really
easy
to
rest
if
I,
that
action,
so
very
simply
I'll
call
this
whisk
create
API
command
and,
in
a
second
we'll
come
back
with
a
URL
boom.
It's
deployed
a
gateway
in
front
of
my
open.
B
Whisk
action
wait
a
second,
this
URL
well
URL
looks
pretty
familiar.
This
is
the
same
URL
that
we
configured
in
slack,
it's
kind
of
all
coming
together.
Now,
let's
take
a
quick
look
at
that
gateway
that
got
generated
when
we
ran
that
terminal
command,
I'm,
switching
here
to
API
Connect,
which
is
our
management
and
gateway
solution
based
on
strong
loop
technology.
B
If
you
guys
recall
that
from
previous
conferences
and
what
we've
got
here
is
plain
old
swagger
and
opens
API
specification,
if
we
wanted
to
use
the
swagger
in
a
other
offering
we
could
do
so,
but
for
the
sake
of
this
demo
we're
using
API
Connect
and
with
an
API
connect,
we
can
also
see
the
visual
representation
of
that
swagger.
Basically,
three
different
API
calls
that
we're
managing
so
quick
overview.
What
have
we
seen
here?
We
posted
a
message
into
the
slack
slack
recognizes
it
calls
our
API
gateway.
B
Our
API
gateway
goes
to
open
whisk,
which
brings
up
a
node.
Runtime
goes
out
to
the
Watson
api's
does
what
it
needs
to
and
then
call
slack
with
the
tonal
analysis.
So
our
footprint
is
tiny
right.
The
compute
power
we're
using
all
we're
doing
is
whenever
a
message
gets
posted
we
bring
up
a
node
runtime,
run
some
script
and
bring
it
back
down
if
no
one's
using
the
slack
bot
our
footprint
is
zero
and
as
far
as
the
API
gateway
goes,
we
are
charged
per
API
call
and
I.
B
A
Thanks
I
appreciate
it
so
we've
so
I
just
showed
us
site
just
showed
us
real,
quick
right.
How
easy
it
is
with
known
and
open
whiskey
and
API
is
to
really
transform
and
do
some
new
engaging
apps
thanks
for
the
time
we've
got
a
lot
of
great
sessions
with
strongloop
and
our
loopback
capabilities
and
core
node.
So
again,
thanks
for
your
time
really
appreciate
it.