►
Description
KEYNOTE: Our Journey and Learnings at the Crossroads of Node.js, Cloud and the Enterprise - Jonathan Carter, Microsoft
Businesses are rapidly turning to Node.js in order to help modernize their applications, improve productivity and enable greater cohesion between teams. And while Node.js usage grows, organizations expect developer tools and cloud services to evolve alongside it, in order to ensure that any gains aren’t lost as the complexity and customer demands of apps increase. Learn how Microsoft is working with the community and enterprises to help grow the Node.js development experience in Visual Studio Code and Azure, including efficient authoring and debugging tools, cloud and Docker-based deployments, and production diagnostics.
About Jonathan Carter
Jonathan Carter is a program manager at Microsoft, working on developer tools and services for JavaScript. He has helped build various things such as the editor, perf profilers and debugger in Visual Studio for Windows and Cordova, the in-browser tools in IE/Edge, an over-the-air distribution platform for React Native, and is now passionate about all things Node.js and Docker/Kubernetes. On the personal side, he enjoys writing comic books that will never be published, traveling with his family, and philosophizing about and everything and nothing at the same time.
A
Good
morning,
everyone,
this
is
my
first
note
interactive,
so
I'm
really
excited
to
be
here.
As
Michael
mentioned.
My
name
is
jonathan
carter,
I'm
from
microsoft,
and
in
this
talk,
what
I
want
to
cover
is
some
of
our
learnings
and
experiences
with
our
customers
using
nodejs
in
the
cloud
and
in
the
enterprise,
and
particularly,
I
want
to
show
off
some
work
that
we've
been
doing
in
Visual
Studio
code
and
Azure
to
help
make
the
developer
experience
a
little
bit
better
for
everyone.
A
So,
as
we've
all
seen
over
the
last
few
years,
the
explosive
growth
of
nodejs
is
very
clear
and
particularly
its
rise
in
the
enterprise
has
also
been
very
significant.
At
Microsoft,
we've
also
seen
a
similar
growth
in
the
number
of
node.js
apps
being
deployed
to
Azure.
Throughout
that
time,
we've
been
able
to
work
with
a
lot
of
really
amazing
organizations,
some
of
which
elicits
here
and
when
we've
talked
to
them
about
their
motivations,
for
why
they
chose
nodejs
for
deploying
to
the
cloud
with
their
production
workloads.
A
We
ended
up
hearing
very
consistent
themes,
many
of
which
we've
all
probably
heard
as
well,
that
Java
scripts
ubiquity
its
applicability
to
full
stack
development.
The
extremely
prolific
community
that
surrounds
it
all
leads
to
one
of,
if
not
the
most
productive
and
collaborative
platforms
today
and
as
organizations
are
looking
to
embrace
new
industry
trends
to
transform
their
business
with
things
such
as
I,
OTE
or
microservices.
Having
a
platform
that
you
can
get
up
to
up
to
speed
quickly,
be
productive
and
be
very
iterative
is
as
important
for
your
bottom
line
as
anything
else.
A
Okay.
Sorry
about
that
that
it's
important
for
the
ecosystem
of
tools
and
cloud
services
to
also
evolve
and
support
those
same
trends
so
that
any
productivity
games
gains
that
you
got
by
using
nodejs,
aren't
lost,
and
so
particularly
when
we've
spoken
with
some
of
our
customers,
we've
heard
three
things
that
developer
tools
need
to
be
fast
and
iterative
regardless,
how
complex
are
simple?
The
application
is
so,
whether
it's
a
mean
stack
app,
whether
it's
microservices,
whether
it's
Polly
glad
it
needs
to
be
fast.
A
It
needs
to
be
iterative
because
otherwise
the
tooling
can
get
in
the
way
that
deployment
to
the
cloud
needs
to
provide
simple
but
flexible
solutions
based
on
OSS
products,
all
of
which
is
based
on
the
standard
of
containers
as
the
artifact
for
deployment.
And,
finally,
the
production
monitoring
is
simple
actionable
and
that
identifying
potential
issues
in
production
can
be
as
simple
and
intuitive
for
developers
in
the
environment
that
they're
in
every
day,
particularly
their
IDE.
A
So
what
I
want
to
do
now
is
jump
into
a
demo,
and
I
want
to
show
off
is
how,
with
Visual
Studio
code
and
Azure
we've
been
trying
to
help
improve
those.
Three
themes
for
nodejs
development
so
for
this
demo,
I'm
going
to
use
a
simple
tutorial
app
from
the
guys
at
scotch
I.
Oh
so
go
ahead
and
clone
that
product
project
and
then
I'm
going
to
open
this
up
in
vs
code.
A
A
So
one
thing
that
we
hear
very
clearly
from
developers
all
the
time
is
that
the
authoring
experience
of
applications
needs
to
be
better
needs
to
be
easier
quicker,
particularly
as
the
application
groves,
and
so
one
thing
that
vs
code
does
is
provide
a
really
great
authoring.
Auto-Completion
experience
out
of
box.
A
So
if
you
know,
as
you
notice,
I
clone
this
project
and
without
having
to
do
anything,
I
can
immediately
get
Auto
completion
on
all
nodes,
ASAP
eyes,
and
the
way
this
is
working
is
that
vs
code
transparently,
is
downloading
typescript
typing's
files
to
drive
the
semantics
that
it
needs
to
understand
the
shape
of
a
pea
is
so
the
first
thing
that
let's
do
is
a
like
all
good
12
factor.
Apps.
Let's
convert
this
DB
connection
from
using
a
hard-coded
string
to
using
an
environment,
variable
so
say,
process
and
will
save
URL
awesome.
A
Additionally,
let's
configure
Mongoose
and
you
notice
as
I'm
typing,
that
I'm
getting
auto
completion
on
Mongoose
as
well,
and
that's
the
same
auto
acquisition
of
typescript
typing's
that
I
just
mentioned
it
doesn't
work
just
for
nodejs
built-in
api's.
It
works
for
over
2,000
third-party
libraries
as
well.
So
what
I
want
to
do
is
just
tell
Mongoose
not
to
tank
whenever
it
can't
connect
to
the
database.
So
say:
oh,
my
god.
Okay,
so
awesome
super
lightweight
super
productive,
editing
experience.
But
what
about
running
this
application?
A
So
let
me
hit
f5
and
you'll
notice
here
the
vs
code
says
hey
what
kind
of
app
do
you
want
to
make
this
so
I'm
going
to
say
no
GS
experimental
and
what
that
means
is
it's
going
to
configure
it
to
use
the
new
node
inspect
debugging
capability,
so
it
generates
this
launched
at
JSON
file,
which
you
notice.
It's
smart
enough
to
understand
what
our
start
script
is
server
ducks
j/s
I'm
going
to
hit
f5
and
you'll
notice.
Now
our
app
is
listening.
A
So
if
I
come
over
here,
here's
the
app
to
book
some
stuff
speak
at
Nina,
I
guess
I
already
did
that
or
I
am
doing
it
and
that's
all
cool
right
so
without
having
to
configure
anything.
I'm
now
running
my
application
I'm
seeing
my
output
logs,
but
what
would
be
even
better
is
if
I
could
debug
this
application
directly
within
the
editor.
A
So
let
me
jump
to
my
routes,
particularly
here
where
I
post
a
new
to
do
I'll
just
come
back
here
and
say
test
and
as
soon
as
I
do
that
I
hit
the
break
point.
Now.
If
I
switch
to
the
debug
tab,
I
have
everything
that
you
would
expect
in
a
debugger.
You
can
hover
over
expressions
and
see
what
their
state
is.
They
can
use
the
debug
console
with
auto
completion
to
evaluate
expressions
live.
A
My
local
swatches
call
stack
everything
works
right,
but
this
app
is
a
mean
stack
up,
and
so,
as
I
mentioned
in
the
beginning,
tools
and
the
inner
loop
needs
to
evolve
in
order
to
help
support
application
development
to
be
easier,
and
so
what
I
want
to
do
is
show
off
a
brand
new
feature
that
we
just
checked
in
a
few
days
ago,
which
enables
the
ability
to
debug
full
front
and
back-end
code.
So
let
me
just
type
drop
in
this.
A
For
the
sake
of
time,
and
now
I'm
going
to
select
this
full
stack
option
and
hit
f5
again
and
now
what
happens
is
is
going
to
run
the
node.js
app.
It's
also
going
to
launch
Chrome.
Let
me
just
refresh
that
everything's
still
working
cool
I
already
had
the
breakpoint
in
the
back
end
code.
But
let
me
go
into
my
angularjs
at
code
and
set
a
breakpoint
in
the
controller
here.
So
I'm
going
to
do
one
more
test.
You'll
notice,
chrome
says:
hey
we're
positive
vs
code,
so
now
I'm
broken
in
front
end
JavaScript,
you'll
notice.
A
In
the
call
psych
window.
We
actually
see
these
two
parallel
nodes
1
for
node.
One
for
chrome
and
I'm
currently
paused
in
chrome.
Once
again,
I
can
see
expression
values
I
can
evaluate
expressions
in
the
console,
etc.
Now,
what's
even
cooler
is,
if
I
hit
run
I
now,
transition
from
the
front
end
to
the
back
end
code.
So
now
I'm
debugging,
no
jazz
code,
you'll
notice
that
the
call
stack
shows
that
and
once
again
everything
just
works.
A
Okay,
so
let's
do
something
else.
So,
as
has
been
mentioned
today,
we've
all
heard
the
craze
of
containers
right.
Everybody
wants
to
run
their
abscess
docker.
It
gives
you
that
repeatable
easy
deployment
capability,
but
it
may
be
intimidating
to
get
started.
Docker,
izing
or
container
izing
your
app
so
envious
code.
You
can
install
the
docker
extension
and
then,
when
I
can
just
do
is
say
docker,
you
know,
add
a
docker
file
to
my
workspace
and
I'm
going
to
say
it's
nodejs,
the
port,
that
this
app
is
exposing
is
8080
and
what
that
does
is.
A
It
goes
off
and
configures
a
docker
file,
dr.
compose
files
automatically
for
me,
so
I
didn't
have
to
go.
Learn
how
to
do
that
I
could
just
kind
of
say
get
it
going,
but
even
better.
We
have
a
good
authoring
experience
for
docker
files
as
well,
so
here
I'll
say
michael
Hart
and
I'm
going
to
use
the
great
Alpine
node.
You
see
it
has
two
hundred
and
forty-eight
stars
image
as
the
base,
because
it's
a
lot
slimmer
than
the
core
node
image
so
now
I'll,
say
docker,
build
and
I'll
tag.
A
It
lost
intention
is
my
docker
hub,
alias
it's
going
to
go
off
and
build
that
image
and
once
again,
I
could
have
used
the
docker
CLI
directly.
I
could
have
gone
and
used
my
own
separate
terminal,
but
these
commands
that
the
docker
extension
adds
just
tries
to
help
make
that
inner
loop
a
little
bit
more
iterative
in
a
little
more
tight.
So
now,
finally,
I'm
going
to
say,
docker
push
and
we'll
push
that
image
up
to
docker
hub
right,
and
so
now
we've
authored,
we've
debugged.
We
can
tailor
eyes
this
application
now.
A
The
name
is
need
a
demo
specify
the
name
space
that
it
goes
in
and
that's
it,
and
by
running
this
one
command.
I
would
now
have
a
past
platform.
That's
capable
of
deploying
a
container
to
now
I
already
created
that
for
the
sake
of
time,
but
what
I
want
to
do
is
configure
it
to
use
the
container
that
we
just
pushed
so
I'm
going
to
have
service
web
config
container
update
the
name
of
it
is
needed
demo.
The
namespaces
in
is
needed
demo,
and
the
container
is
ok,
that
was
nice.
A
Let's
try
that
again
app
service
web
config
container,
update,
Nina
demo
new
demo
and
the
container
is
lost
in
tangent,
/
node,
yeah
I
was
hyping
up
hyper
and
then
I'll
sinitta
has
this
rendering
issue
okay.
So
what
we
just
did.
Is
we
configured
that
to
just
pull
our
container
that
we
deployed
a
docker
hub
and
spin
that
up
so,
let's
say
AB
service
web
browse
being
a
demo
and
get
demo?
A
So
it's
going
to
launch
that
path
based
service
that
we
just
deployed
our
container
to
so
here
we
go
I'm
a
to
do
a
holic,
as
we
all
are,
but
unfortunately
you'll
notice
that
it's
spinning
and
the
reason
is
because
that
the
doc,
the
mongodb
instance
that
I
had
running
locally
is
not
available
in
the
cloud.
And
so
what
we
need
to
do
is
give
configure
that
connect
the
environment
variable
that
we
specified
so
I
could
go
off
and
deploy
my
own
instance
of
doc,
DB
or
MongoDB.
A
But
in
Azure
we
actually
have
a
pass
based
solution
that
makes
this
simple
to
manage
its
geo,
replicate
replicable
and
makes
it
just
that
much
easier
for
you
to
have
to
build
your
applications.
So
I
already
provision
that
up
in
the
portal,
so
we'll
come
in
here
I'll
say
getting
started
and
on
the
nodejs
tab,
I'm
going
to
go
ahead
and
just
grab
this
connection
string
and
I'm
going
to
go
back
to
my
appt
service
instance,
which
is
right
here
and.
A
So
in
a
second
that
should
be
successfully
created,
and
so
now
the
effect
is
that,
just
like
a
12
factor,
app
changing
config
is
just
like
changing
code.
The
net
effect
is
that
when
I
refresh
this
app,
it
actually
should
be
able
to
connect
successfully
to
doc
DB.
So
it
will
test
this
and
now
that
works,
and
so
as
the
throughput
demands
on
my
application
or
my
data
layer,
grow.
A
I
can
go
back
in
here,
and
the
beauty
of
doc
DB,
as
I
mentioned,
is
that
I
can
scale
it
without
having
to
do
any
of
that
management.
So
I
can
just
come
in
here
and
say:
hey
the
to
do's
collection.
I
need
to
double
triple
increase
the
throughput.
I
need
to
replicate
it
to
South,
South,
America,
etc
and
I
don't
have
to
worry
about
how
many
of
that
works.
A
Ok,
so
that,
with
that
demo,
right
kind
of
highlighted,
some
of
the
basics
of
vs
code
showed
how
hey
we
want
to
make
full
stack
development
simpler
for
polyglot
full
stack
apps.
We
want
to
make
it
easy
to
container
eyes
your
applications
and
then
deploy
them
to
the
cloud
by
using
simple
pass
based
solutions,
but
also
using
docker
as
that
standard
deployment
artifact.
So
let's
switch
back
to
the
slides
so
just
to
kind
of
wrap
up.
A
If
you
haven't
seen
or
your
aren't
familiar
with
vs
code
or
azure-
and
you
thought
any
of
what
I
just
showed
was
interesting.
I
would
encourage
you
to
go
check
it
out.
Ezra,
calm,
/,
node,
but
also
please
come
and
talk
to
us
we'll
be
at
the
booth
all
week.
That's
my
email,
github
and
Twitter
information,
the
more
feedback
and
the
more
collaboration
that
we
have
with
the
community
and
our
customers.
The
better
right.
A
So
almost
everything
I
showed
today
is
already
open
source
and
we
have
quite
a
bit
more
things
that
we're
working
on
that
I
wasn't
able
to
capture
that.
We
really
really
really
want
to
work
with
the
community
as
much
as
we
can,
because
we
love
nodejs,
and
we
just
know
that
the
potential
image
is
extremely
great.
So
so
with
that,
that's
all
that
I
have
so
I
really
appreciate
it
and
hope
to
talk
to
you
guys
later
of
the
week.