►
From YouTube: Building Scalable Web Applications Using Microservices Architecture and NodeJS inside AWS Lambda
Description
Building Scalable Web Applications Using Microservices Architecture and NodeJS inside AWS Lambda - Eugene Istrati, Mitoc Group Inc
Scalable applications are by nature resource intensive, expensive to build and difficult to manage. What if we can change this perception and help developers design full-stack applications that are low cost and low maintenance? This session describes the underlying architecture behind www.deep.mg, the microservices marketplace built by Mitoc Group using AngularJS, NodeJS and powered by abstracted services like AWS Lambda, Amazon CloudFront, Amazon DynamoDB, and so on. Eugene Istrati, Technology Partner at Mitoc Group, will dive deep into their approach to microservices architecture using serverless environments from AWS and demonstrate how anyone can use serverless computing to achieve high scalability, high availability, and high performance without huge efforts or expensive resources allocation.
A
A
A
A
Okay?
Well,
thank
you
guys.
Well,
my
name
is
Eugene
I'm,
the
technical
partner
at
the
startup
based
in
New
York
tech.
My
tech
group,
I,
developer
I
use
I'm
working
as
a
developer.
Since
high
school
I'm
worked
for
the
last
seven
years,
with
AWS,
going
through
all
the
phases,
starting
with
the
time
when
they
launched
the
Amazon
s3
I'm
a
certified
solution.
Architect
and
I
worked
at
companies
like
Amazon
Web,
Services,
Hearst
Corporation
grab
hub
when
it
wasn't
a
start-up.
A
The
company
mitre
group
is
focusing
on
we're
officially
technology
partner,
a
double
technology
partner,
and
we
have
featured
database
lambda
partners.
Okay,
so
today,
I'll
try
to
explain
you
as
much
as
I
can
a
couple
of
major
concepts.
What
is
serverless
computing,
what
is
microservices
architecture
and
why
no
js'
is
important
in
this
ecosystem.
A
So,
let's
start
with
the
server
list.
What
does
serverless
mean?
Okay
in
a
nutshell,
it's
something
involved
with
no
servers
right.
So
to
be
precise,
we
as
developers
don't
need
to
think
about
those
servers,
especially
at
scale.
We
get
sis
we
get
the
access
to
services
right
and
we're
just
using
them,
as
you
would
use
your
servers,
but
the
best
way
to
describe
what
is
several
is
I
like
this
guy.
A
Now
look
around
okay,
so
we've
published
last
year
a
couple
of
blog
posts
and
couple
of
videos
how
to
do
it
service
on
AWS,
so
I
won't
spend
too
much
time
if
you're
interested
take
a
look
by
the
way.
At
the
end,
this
is
posted
on
a
SlideShare.
If
you
guys
need
some
feel
free
to
take
pictures,
but
if
you
need
don't
worry,
it's
on
the
slide
sure
now,
serverless
concept.
A
They
can
be
applied
anywhere
either
way
talking
about
infrastructure.
Are
we
talking
about
a
platform?
Are
we
talking
about
the
application
right,
I
personally
like
to
think
of
micro
services
as
a
shredder
for
software
that
makes
from
a
big
and
complex
into
a
small
and
simple,
but
because
it's
a
shredder,
you
get
a
lot
of
small
pieces
that,
if
you'll
take
it
manually
to
put
them
back
together,
you're,
crazy,
okay,.
A
So
if
it's
software
driven,
you
can
design
it
to
the
micro
services.
Ok,
micro
service
architecture
is
also
a
very
new
trend
that
it
gets
a
lot
most
of
us
very
excited,
very
eager
to
try
it
and
that's
why
it's
so
surprising.
The
two
years
ago,
according
to
Google
Trends,
this
term
didn't
even
exist
as
a
backstory,
the
guy
that
works
for
inside
the
database,
lambda
team.
A
Before
that
he
worked
at
Microsoft
on
the
being
team,
and
he
told
me
yeah,
that's
exactly
what
we're
doing
at
the
bean,
but
we're
not
calling
them
micro
services
right.
So,
finally,
let's
get
to
a
hands-on
demo.
That's
what
I
would
like
to
show
you
and
point
out
where
nodejs
plays
a
big
role
before
doing
that
like
to
do
an
architectural
review
right,
what
does
it
mean
to
build
scalable
applications
using
serverless
computing
and
micro
services
architecture?
A
Ok,
so
all
of
these
services
that
you
are
seeing
here,
there
are
two
four
eight
nine
services
and
then
this
is
just
the
foundation
right
and
that's
I.
Don't
have
the
SSH
terminal
to
login
to
try
to
manage
my
servers
and
I
actually
don't
need
it.
In
my
experience
as
a
developer
prior
to
you,
starting
using
this
approach,
I
was
spending
70,
80
percent
of
my
time,
dealing
with
something
that
is
not
applicable
to
application,
mostly
to
our
infrastructure,
to
the
platform
and
so
on.
So
the
request
comes
in.
A
It
goes
to
a
DNS
right,
the
DNS
resolve.
It
goes
to
an
CDN.
The
CDN
points
to
a
hosting
service
which
a
lot
of
people
don't
even
realize
that
s3
can
be
used
as
a
hosting
service.
Right
then,
from
the
s3
you
make
calls
to
JavaScript
and
I
wish.
I
would
have
this
talk
before
Sarah
now,
I
have
to
say
I'm
on
the
dark
side.
Right
and
so
JavaScript
makes
call
to
API
gateway,
and
it
also
uses
a
service
that
it's
called
kognito.
A
A
Then
it
goes
to
an
API
gateway,
a
KPI
gateways.
Just
proxy,
but
it
is
uploads
a
lot
of
the
pain
points
of
how
do
you
set
up
restful
api
is
how
do
you
set
up
throttling
metering
and
so
on
and
so
forth,
and
then
it
goes
to
the
lambda,
which
is
the
core
compute
service.
It's
just
the
container,
a
self
managed
container
service
right,
that's
that's
the
back
end
and
then
you
can
go
to
dynamo.
Db
dynamo.
A
Db
is
a
great
knows,
no
sequel
of
ski
key
value
pairs
database,
but
it's
very
it
might
be
very
cost
intensive
at
scale,
and
so
that's
why
we
have
on
the
Left.
We
are
floating
the
reads
to
caching
mechanism
like
elastic
cache.
Well,
sorry,
I
meant
memcache
or
Redis
and
on
the
right,
it's
a
queuing
mechanism
right
where
you
for
the
use
cases
that
you
have
the
eventual
consistency,
use
cases
you
can
offload
and
get
them
into
your
database
a
couple
of
seconds
later,
maybe
a
minute
later,
it
depends
on
in
this
case.
Okay.
A
So
this
is
the
architectural
diagram.
I
will
not
be
going
into
the
whole
code
of
these
websites.
That's
the
websites
we're
working
on,
but
I'll
show
you
a
smaller
application,
which
is
as
relevant
as
this
one.
Okay,
it's
called
to
do
MVC
right,
so
let
me
switch
to
the
terminal,
okay
and
let
me
switch
actually
to
yeah
this
one
so
to
do
MVC
it's
just.
We
took
the
code,
the
front-end
code
from
the
to
the
MVC
repository,
and
we
just
apply
to
this
service
architecture
using
micro
services.
A
The
service
computing
is
this
micro
services
architecture,
so
I'll
just
follow
these
steps.
First
step
is
to
set
up
write
all
the
prerequisites
in
order
to
be
able
to
use
it
and
I
hope.
You
guys
trust
me
that
I
already
have
installed
DP
Phi
on
my
local
machine
and
I
just
wanted
to
show
you
over
here
there.
The
version-
and
this
is
the
command
line-
to
streamline
all
the
development
deployment,
testing
and
so
on.
A
Then
the
next
step
is
just
to
try
to
install
well
not
to
try
but
install
it
locally.
Okay,
so
what
it
does
our
deep
if
I
command
it
works
with
the
with
repositories
and
with
github
and
works
with
registries,
are
not
repositories
with
the
registers.
So
it
successfully
installed.
Let
me
show
you
what
includes
it
includes
the
code.
It
has
the
front
and
the
back
end
database
setup,
and
it
includes
the
deploy
JSON
file.
A
Now,
let's
go
back
to
run
it
locally
or
to
run
it
in
development.
We
simulating
local
everything.
We
simulating
the
front
lambda,
which
is
just
a
darker
container
on
the
localhost,
we're
simulating
the
DynamoDB,
it's
just
a
local
dynamodb.
That's
how
the
package
is
called
database
provides
and
we're
simulating
the
s3,
which
is
basically
hosting
service
your
filesystem.
There
is
nothing
to
simulate
there.
A
Okay,
now
what
you've
seen
a
dependency,
pull
the
dependency
okay
and
mainly
because
lambda
doesn't
support
node
6.6
and
was
announced
today
the
highest
version
that
they
support
is
4.3.
That's
why
we
have
a
lot
of
complexity
added
into
DP
Phi
that
compiles
back
right
to
4.3,
okay.
So,
while
it's
compiling,
let
me
just
show
you
what
what
it
looks
like
right.
A
So
this
is
the
website.
I,
don't
know
if
anyone
used
to
do
MBC
before
to
build
some
of
their
capabilities
or
to
show
some
of
that
or
to
test
it
out
or
learn
how
to
use
other
JavaScript
frameworks
like
angular,
JS,
react.js
and
so
on,
but
it's
a
very
Google
tool
to
go
get
started
again,
while
it's
compiling
yeah
just
remember
so
we
as
a
team.
We
said
we
enforced
a
year
six
standard
weeks,
2016
2016,
2015,
no
2015.
We
imposed
on
our
teams.
A
What
will
that
will
be
using
yes,
six
standard
right
and
again,
because
lambda
is
version
4.3.
We
need
to
use
babel
to
transpile
that
code
in
order
to
upload
on
lambda
again,
while
it's
compiling
it
will
take
a
little
bit
time.
First
time
as
you've
seen,
yeah
I
started
from
scratch.
It
takes
a
little
bit
of
time.
Next
iterations,
because
it
just
does
NPM
we're
using
NPM
on
the
back
end
because
it
does
NPM
update
it.
It
goes
faster.
A
There
is
a
small
inconvenience
in
world
aside
that
you
can
not
use
known
six
point.
Six,
there
is
a
small
inconvenience
and
when
lambda,
if
your
code,
this
big
a
small
area
code,
the
faster
it
works
right.
So
that's
why
another
thing,
because
you
do
a
lot
of
these
transpiling
and
you
generate
a
lot
of
the
NPM,
pulls
all
the
dependencies
as
well.
You
want
to
optimize
all
of
that
right
either
you
doing
it
by
yourself.
Do
it
yourself
it's
very
easily
or
you
use?
A
That's
that's
what
we've
done
all
of
this
work
in
order
to
pull
the
dependencies
to
optimize
to
make
the
package
that
is,
the
zip
file
that
is
loaded
or
native
is
lambda
as
small
as
possible
and
by
the
way,
we're
talking
about
scalability
we're
doing
this
at
scale
right
so
for
the
applications,
the
architecture
that
I
showed
you
before
we
have
120
microservices
I.
Imagine
you
start
deploying
all
of
this
at
once
right.
First
of
all,
don't
do
it!
A
Finally,
it's
done
and,
as
you
can
see,
it's
localhost
port
8000
and
runs
exactly
the
same
application,
okay
and
just
to
because
I'm
running
a
little
bit
out
of
time.
Sorry
guys,
the
last
step
is
deploying
it
takes
that
everything
that
you
have
compiled
locally
it
packages
and
it
uploads
it
all
native
is
lambda,
but
besides
that
it's
not
just
data
based
lambda,
as
you
saw
in
the
architecture,
it's
I
I
talked
about
nine
services
that
were
using
it.
A
Pre
pre
provisions,
the
services
provisions
all
the
resources
that
the
services
make
them
configuring
the
security,
because
we're
using
I
am
Identity
and
Access
Management
to
manage
all
the
services
and
by
the
way
it's
secure
by
default.
It
doesn't
work
if
you
don't
set
up
the
security,
that's
how
it
works.
Okay.
So
let's
switch
back
to
the
presentation.
A
I
would
just
like
to
call
out
this
framework,
which,
in
theory,
is
an
OG,
it's
an
ojs
library
or
a
collection
of
node.js
libraries.
It
deals
with
the
deals
with
every
service.
Every
aw
service
in
an
abstracted
mode,
it
doesn't
say,
go
on
s3
I,
take
the
file,
it
says,
go
on
the
file
system
and
take
that
file.
Write
it
abstracts,
you
so
use
a
developer.
You
can
use
it
very
simply
and
if
you
don't
know
how
to
use
those
nine
services,
you
don't
even
need
to
know
how
to
use
them.
A
A
A
A
Slideshare
is
actually
uploaded,
but
in
just
the
first
couple
of
slides
on
Lincoln
s,
the
slides
will
be
uploaded
on
SlideShare
sorry
and
we
have
a
couple
of
blog
posts
and
we
keep
posting
about
servers,
computing
micro
services,
architecture
AWS
on
on
the
medium,
if
you
guys
interested,
feel
free
to
go,
there
read
and
leave
your
comments.
I'd
like
to
thank
a
be
and
I
would
like
to
thank
the
team
from
a
Linux
Foundation
that
put
it
all
this
together.
So
I
have
one
minute
and
a
half.
If
there
are
any
questions.