►
From YouTube: Node.JS and Containers Go Together Like Peanut Butter and Jelly - Ross Kukulinski, NodeSource
Description
Node.JS and Containers Go Together Like Peanut Butter and Jelly - Ross Kukulinski, NodeSource
"A recent Node.js Foundation survey found that 45% of developers surveyed use Node.js with containers. As companies look to build out their microservice architectures, Node.js is emerging as a major component for powering Internet-scale computing.
Additionally, JavaScript, including Node.js and frameworks such as React, are becoming the de facto choice for IoT developers working in connected, device-driven environments, according to the recent survey.
However, these environments are challenging, for even for the most experienced developers out there. In this presentation, Ross Kukulinski, a NodeJS Evangelist and container enthusiast, will discuss why Node.js has become a popular choice in microservices-oriented, containerized dynamic environments. He will discuss how to get started with Node.js, Docker and Kubernetes and what pitfalls often occur when starting and how to avoid them."
A
Good
morning,
good
morning,
how
was
day
one
alright
cool,
so
I'm
gonna
be
talking
about
nodejs
and
containers
and
why
they
go
so
well
together.
But
of
course,
when
I
name,
this
talk
I
had
never
been
Amsterdam
before
so
maybe
we
should
actually
call
this
Fry's
and
mayo,
which
apparently
people
love
here.
A
So
my
name
is
Roscoe
kolinsky
I'm,
a
product
manager
at
node
source
I'm.
Also,
a
member
of
the
node
evangelism
working
group,
so
I
go
to
meetups
and
come
to
events
and
try
to
convince
everybody
that
node
is
the
greatest
thing
in
the
world.
I've
also
been
working
with
containers
for
a
long
time,
so
I've
been
working
and
trying
to
figure
out
how
to
scale
node
with
containers
and
orchestration
systems
for
a
couple
years
now
and
I've
got
an
introduction
to
core
OS
video
tutorial
series
by
O'reilly,
so
here's
today's
roadmap.
A
A
Okay,
why
node
in
containers
now
before
we
dive
into
the
technical
aspects?
Let's
talk
about
business
because
at
the
end
of
the
day,
most
of
us
here
are
working
for
companies
and
companies
like
to
make
money.
Businesses
need
to
innovate
faster,
the
quicker
they
can
get
a
product
out
to
market
the
sooner
they
get.
Feedback
from
users
means
that
they
can
build
better
products
and
better
services,
and
if
you
do
that,
you
execute
that
you
profit,
your
business
is
successful.
A
You
keep
getting
paid,
you
get
to
do
it
again
next
month,
okay,
great
well,
noting
containers,
accelerate
innovation.
I'm
gonna
tell
you
why
noting
containers
both
excel
in
three
key
areas:
performance,
packaging
and
scalability?
Well,
let's
dive
into
that
now
from
a
performance
perspective.
There's
a
couple
of
ways:
you
can
analyze
performance,
yeah,
sure,
there's
technical
performance,
but
let's
talk
about
from
a
business
perspective.
A
What's
your
most
expensive
aspect
of
your
business,
your
people,
so
if
we
can
do
anything
to
make
our
developers
or
operations
teams
be
able
to
build,
faster,
create
and
innovate
new
features
and
new
capabilities
faster.
That
means
that
as
a
business
work
cellaring
our
innovation
and
note
does
this
right.
So
we've
got
this
notice.
It's
got
this
extensive
package
ecosystem,
so
developers
become
system
integrators,
we're
pulling
together
bits
and
pieces
of
code
to
build
larger
applications
faster.
Also,
it's
fun.
I
love,
developing
a
node,
happy
developers
are
gonna
stick
around.
A
It
also
means
that
you
can
help
retain
your
top
talent
and
bring
in
new
talent.
So
that's
the
people
problem.
What
about
technology
well,
node
helps
solve
the
c
10
k
problem.
That's
10000,
concurrent
connections.
This
was
originally
written
in,
like
the
original
thing
was
in
1998
or
something
when
nobody
10,000
connect.
Concurrent
connections
is
like
crazy.
Now,
no
it
solves
this
problem,
so
node
can
be
inserted
as
your
api
gateway.
A
If
you
want
to
roll
out
a
new
mobile
application
or
new
website,
it's
going
to
be
smashingly
successful,
but
maybe
your
existing
infrastructure
was
not
built
to
handle
all
those
connections.
Node
can
be
dropped
in
to
handle
that
and
offload
that
from
an
existing
infrastructure,
and
then
what
we've
seen
is
because
developers
enjoy
building
it
and
our
faster
building
with
node
node
starts
to
pop
up
everywhere
else.
In
your
infrastructure.
It's
that's
not--.
How
about
containers?
Well,
containers
have
lower
overhead
so
compared
to
virtual
machines,
where
you
have
an
entire
operating
system.
A
A
It
also
enables
developers
to
own
the
deployment
cycle,
and
this
is
giving
rise
to
this
DevOps
word,
which
means
everything
to
everybody
else,
but
at
the
end
of
the
day
developers
want
to
ship
applications.
They
don't
wanna
ship
virtual
machines,
they
don't
want
to
ship
a.m.
eyes.
You
want
to
take
their
application
and
just
ship
it
and
a
container
is
a
nice
tight
little
box
right
around
their
application,
so
it
enables
those
developers
to
ship
that
and
own
that
whole
cycle
packaging.
A
Note
again,
he's
got
this
extensive
module
ecosystem
and
we
have
an
explicit
application
dependency
manifest.
That's
your
package
JSON,
you
explicitly
say:
npm,
install'
save
or
s.
If
you're
fancy
all
these
dependencies,
when
you
run
your
npm
install
you're
gonna
get
a
repeatable
dependency
installation
you're
gonna
get
those
same
packages
again.
A
So
if
you
hand
your
node
app
to
somebody
else
and
they
install
it,
they're
gonna
get
the
same
stuff
when
you
tie
that
with
containers,
containers
also
have
an
explicit
build
manifest
that
your
docker
file,
it's
a
recipe
that
describes
exactly
how
to
build
this
image,
and
once
that
image
is
built,
it's
immutable.
You
can't
change
it.
If
you
change
it,
you
are
getting
a
new
image
so
because
it's
immutable,
if
I
have
this
image
and
it's
running
in
production,
I
can
pull
down
that
image
and
run
it
locally.
A
It's
the
same
code,
and
so,
if
there's
a
problem
with
an
application
in
production,
that's
fine!
Maybe
we
move
it
from
rotation,
so
it
stops.
Servicing
traffic.
I
can
pull
that
image
down
and
I
can
start
to
load
test
it
locally
and
try
to
figure
out.
Why
is
it
not
working
as
it
should
and
that's
running
anywhere,
whether
it's
on
your
development
machine
in
QA
and
test
production
across
multiple
cloud
providers?
A
Scalability
this
one
I
love
so
node
scales
at
the
process
level,
which
makes
it
easy
as
a
developer.
You
don't
have
to
worry
about
thread,
locking
and
all
this
other,
you
know
weirdness
with
Java
or
C,
or
some
of
these
other
languages
that
we've
had
to
work
with
before
we
write
our
node
app.
It
sits
in
just
a
single
process.
You
need
more
scale,
run
more
of
them
done
notice.
Fastboot,
are
you
run
node,
my
app
and
a
well-written?
A
No
doubt
it's
up
ten
milliseconds
50
milliseconds
fast
and
we've
already
talked
about
the
concurrency,
so
node
can
handle
those
large
number
of
connections
that
we're
seeing
in
these
new
cloud
deployments
and
cloud
applications,
and
then
you
pair
that
with
containers
containers
also
scale
at
the
process
level.
You
everyone,
you
run
one
process
per
container
and
if
you
need
more
scale,
you
run
more
containers.
They
fit
perfectly
together,
like
that.
Containers
are
fast
the
boot.
So
if
you
have
a
fast,
no
tap
a
fast
container,
you
can
now
scale
up
your
application
incredibly
quickly.
A
One
of
the
other
nice
things
about
containers
is
that
the
scaling
is
not
tied
to
your
cloud
provider.
So
if
your
current
deployment
process
is
alright,
we
need
to
scale
up
so
we're
gonna,
ask
Amazon
or
Google,
give
me
ten
new
virtual
machines
or
100
new
virtual
machines.
How
long
is
that
going
to
take
if
you
already
have
some
of
that
infrastructure
ready
to
go
with
containers
you're,
just
asking
your
orchestration
system
give
me
ten
more
and
you
can
also
scale
on
a
per
process
basis.
A
So
if
your
website
shows
up
on
reddit
or
it's
on
product
hunt,
and
suddenly
you
get
a
ton
of
hits,
you
can
scale
up.
Maybe
your
friend
and
website,
leaving
your
API
servers
alone
may
be
leaving
your
databases
alone,
but
if
you
are
launching
a
new
product,
you're
expecting
lots
and
lots
of
signups
they're
gonna
crank
up
your
website
and
your
API
server
that
handles
logins.
That
way,
you
can
independently
scale
each
aspect
of
your
application
as
a
whole,
so
containers
a
node
make
developers
and
businesses
happy.
A
There's
not
a
lot
of
things
that
do
that.
This
is
one
of
the
reasons
that
I'm
so
excited
working
with
node
in
containers.
Okay,
so
Ross,
you've
convinced
me
we're
gonna
containerize,
all
the
things
great
now.
What
well,
if
your
architecture
looks
kind
of
like
this
very
simple
client
might
be
mobile
app
website.
Maybe
you
stick
a
load.
Balancer
you've
got
a
single
tier
of
applications
you
into
a
database.
It's
a
pretty
simple
three
tier
by
that
you
can
manage
these
containers
using
configuration
management
tools
like
ansible
puppet
chef.
A
You
can
use
docker
swarm
and
Amazon's
ECS
or
elastic
container
service.
But
if
you're
like
me-
and
you
tend
to
write
more
complex
things
the
moment-
a
customer
asks
for
things.
Maybe
architecture
looks
kind
of
like
that,
with
different
teams
using
different
languages
and
different
services,
and
this
team
wants
to
use,
rethink
TB
and
this
team
wants
to
use-
and
this
team
is
over
here-
is
using
Redis.
A
We're
gonna
need
some
orchestration
help.
How
do
we
handle
dealing
with
all
of
these
independent
moving
pieces
and
in
a
traditional
deployment
process?
You
probably
have
to
write
your
own
orchestration
system
and
probably
most
of
us
or
some
of
us
probably
have
I
know
of
written
at
least
two
or
three
of
these
and
I.
Don't
like
writing
orchestration
systems.
A
I
want
to
focus
on
building
a
business
value,
building
features
and
capabilities
that
are
gonna,
make
my
customers
happy
and
pay
us
more
so
that
I
can
do
it
again
next
month
and
that's
where
kubernetes
comes
in
the
kubernetes
is
an
open
source
system
for
automating
deployment,
scaling
and
management
of
your
containerized
applications.
Okay,
so
that's
a
mouthful,
that's
straight
from
the
website:
let's
live
our
real
talk.
What
does
kubernetes
buy
you?
So
kubernetes
schedules
your
containers
onto
physical
machines.
A
So
if
you've
got
a
hundred
machines,
kubernetes
knows
how
much
CPU
memory
is
on
each
physical
host.
It
knows
what
pods
or
containers
it's
already
scheduled,
how
much
memory
and
CPU
they
need,
and
it
can
figure
out
where
to
put
them
to
make
sure
that
loading
is
averaged,
and
then
we
get
pretty
good
users
resource
utilization.
True
Bonetti
is
also
does
service
discovery
and
load
balancing,
so
you've
got
all
of
these
applications
back
here
then,
there's
all
these
interconnections.
How
do
your
apps
find
and
talk
to
each
other
well
kubernetes
helps
with
that.
A
A
Kubernetes
includes
horizontal
application
scaling,
so
you
can
specify
hey
if
my
pods
are
above
or
if
my
containers
for
a
certain
application
on
average
or
above
let's
say,
50%
CPU,
make
more
of
them,
bring
that
average
down
and
we're
able
to
make
sure
that
we
have
a
consistent
latency
profile
or
whatever
your
key
business
metrics.
Are
it
also
handles
automated
rollouts
and
roll
backs
and
I'm
actually
gonna
demo?
A
So
when
you
build
your
image
or
you
build
whether
you're
building
your
application
or
building
your
docker
file,
your
image,
you
don't
really
want
to
inject
secrets
in
there
TLS
keys-
or
maybe
your
database
passwords,
because
that
container
is
going
to
sit
on
a
register.
It's
the
same
reason:
we
don't
check
in
keys
to
github,
don't
check
in
keys
into
your
docker
file,
but
you
still
have
to
have
that
somewhere.
A
A
A
Yes,
so
kubernetes
has
a
CLI
tool
called
Kuby
control
that
allows
us
to
interact
with
the
rest
api.
Now.
All
of
this
is
secured
by
TLS
and
all
sorts
of
nice
things.
So
I
feel
safe
running
this
even
on
conference.
Wi-Fi
I
also
have
VPN
so
go
me
and
because
I
don't
ever
want
to
battle
the
demo
gods.
I
have
a
nice
readme.
That's
gonna
make
sure
that
I
don't
miss
anything
okay.
So
let's
look
at
our
app
first,
so
I
have
a
very,
very
simple
node.js
application.
A
This
app
listens
on
a
predefined
port
or
port
3000
and
it's
got
three
routes.
It's
got
a
health
request,
health
Z.
So
if
we
hit
that
we
just
say
yeah
sure
we're
healthy,
we
probably
should
do
a
better
health
check
number
two.
If
we
hit
the
URL
slash
version,
we
respond
with
the
version.
That's
in
our
package,
JSON.
A
We
can
run
this
so
here's
our
app
note,
indexed
fjs
and
let's
hit
localhost
3000,
that's
a
little
small
hello
world,
alright
and
for
lucky
I'm
running
version,
1,
oh
and
if
I
were
lucky,
I
respond.
Yeah
version
1
now
I've
already
built
a
docker
image
for
this.
So
we
can
take
a
look
at
the
docker
file.
Oh
it's!
So
this
is
a
pretty
standard,
docker
file
for
me,
I've
done
other
talks
on
like
docker
file
best
practices.
A
I've
got
a
github
repo
with
some
of
this,
but
basically
we
copy
our
know
tap
into
the
docker
file,
we're
using
dumb
in
it
from
the
Yelp
team
to
make
sure
that
we
properly
handle
signals
and
we
run
around.
That's
it.
Nothing
fancy
here
so
with
that.
Let's
deploy
our
app
I've
already
built
and
pushed
this
image
because
I
didn't
want
to
consume
conference
Wi-Fi.
A
So,
let's
roll
this
out
and
let's
make
sure
that
I
type
this
right
so
we're
gonna,
use,
coupie
control
and
we're
gonna
run
we're
gonna,
create
a
new
application
or
what
kubernetes
calls
a
deployment
and
we're
gonna
call
this
hello
world
and
if
we
specify
our
image.
So
my
image
is
raw.
Squid
kolinsky,
slash
hello
world
and
I
always
tag
my
images
so
that
I
know
exactly
what
that
is.
For
those
of
you
maybe
have
worked
with
docker
before
when
you
build
an
image.
A
If
you
don't
specify
a
tag,
the
tag
is
latest,
don't
ever
use
latest
because
the
next
time
someone
pushes
guess
what
happens
latest
is
no
longer
the
latest.
You
thought
it
was
so
if
you're
gonna
build
images,
tag
them
with
a
version.
Maybe
it's
from
your
package
JSON.
If
you're
using
CI,
CD
user
get
sha,
maybe
a
build.
If
you
have
unique
build
the
numbers
that
way
you
can
run
when
you
reference
an
image,
it's
always
gonna
be
the
image,
as
you
expect
it
to
be.
A
We
need
to
specify
which
port
that
kubernetes
should
expose.
So
let's
use
port
3000
and
we
can
specify
the
number
of
replicas.
So,
let's
start
with
3,
we
don't
want
to
overload
our
system
and
then
I'll
talk
a
little
bit
about
labels
later
on,
but
we
basically
want
to
set
our
label
is
a
people's
hello
world.
Now
you
know
real
world
you're,
probably
not
actually
running
commands
like
this.
It's
nice
for
demos,
kubernetes
has
API
definition,
spec
files
and
it's
either
yam
large
Ehsan.
A
A
So
kubernetes
has
this
definition
of
what
a
pod
is.
A
pot
is
basically
a
logical
grouping
of
one
or
more
containers
that
should
reside
on
the
same
physical
host.
They
should
actually
their
networking
and
share
their
file
system
is
shared
reality
most
of
the
time
when
I'm
working
with
node
I
just
have
one
container.
It's
my
node
app
in
that
pod.
A
Maybe
if
I
need
to
have
a
cache,
a
local
cache
to
specific
to
that
instance,
then
I
might
read
it
run
Redis
or
some
other
mat
remember
cache
as
a
separate
container
in
the
same
pot
in
general,
one
pod
per
container
one
container
per
pod,
great,
so
they're
running,
that's
cool!
Now
I
already
went
ahead
and
created
a
service.
So
kubernetes
has
this
definition
of
what
a
service
is.
The
service
enables
you
using
that
label
app
equals
hello
world
and
in
fact,
if
we
describe
this
service.
A
Will
notice
that
the
selector
here
what
this
service
does
is
it
looks
at
all
of
the
pods
that
are
running
in
the
system
and
any
pod
that
has
the
label
app
equals
hello
world.
If
a
request
comes
in
to
this
external
IP
address,
this
is
actually
a
Google
load,
balancer
IP
address.
So
if
you've
got
a
computer,
you
can
actually
hit
this
IP
address.
A
Crudities
does
this
in
a
very,
very
nice
elegant
way
and
that's
rolling
deploys,
so
you
want
to
roll
out
a
new
version
and
you
want
to
roll
it
out
one
instance
at
a
time
or
groups
of
five
or
groups
of
ten,
and
you
want
to
have
configuration
of
how
fast
and
what
sort
of
checks
should
be
done.
Kubernetes
does
that
so
we're
gonna
do
a
live
edit
of
our
deployment
now
I
have
also
pushed
out
a
version
two
of
my
deployment.