►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
B
Ok
then,
let's
go.
Let's
start
thanks
to
everyone
good
morning
to
the
entire
Hispanic
community
that
is
listening
to
us.
Thank,
you
very
much
for
being
with
us.
Today.
I
want
to
tell
you
about
some
things.
The
truth
is
that
many
times
we
talk
about
different
things
and
the
world
of
Java
is
like
saying,
very
broad,.
There
are
many
myths,.
B
They
talk
about
many
things,
and
I
What
I
want
is
for
us
to
practice
a
little
bit
of
that
and
I've
been
working
with
him
for
a
while
now,
as
Alberto
said,
I've
been
working
with
him
for
almost
23
years..
It
has
been
in
the
communities
implementing
different
things
that
we
did
not
from
different
implementations
of
those
that
we
used
because
I
do
not
know
some
bumps
some
online
commands.
B
We
had
complications
with
the
manual
compilation
until
now
that
everything
requires
pipeline
automation
and
many
things
that
we
are
needing
and
advancing
With
putting,,
let's
develop
ourselves
and
what
modern
applications
are,
so
I
want
to
share
as
a
team.
What
I've
seen
in
recent
years
regarding
microservices,
these
microservices
are
suddenly
in
fashion
and
bring
us
many
benefits,,
but
nevertheless,
things
are
not
working
completely,
as
we
thought.
Something
should
be
working
is
important.
B
Anything
you
think
he
said
a
strange
word
remember
that
we
have
several
Spaniards,
and
so,
whatever
you
think
I
say
I
didn't
say
if
it's
rude
or
a
very
strange
word.
No,
so
there
is
unharmed
and
that
e
ncargo,
no
good
something
something
that
is
interesting
is
that
all
of
you
are
here
behind
this
computer.
B
Well,
we
are
not
going
to
create
a
new
netflix.
Normally
that
is
netflix
is
already
created.
Well,
it
is
working
on
flix
and
you
can
go
to
increase
the
services
functions
and
so
on,
but
We
are
not
going
to
implement
it
from
scratch,
so
many
times
the
requirements
that
we
have
sound
like
they
make
us
really
want
to
implement
new
things,
generate
fun,.
They
will
start
looking
for
different
situations,
different
patterns,
defense,
architectures,
however,.
The
question
is
really
what
we
need
is
that..
B
Well,
I
think
that
many
times,,
not
many
times,,
when
we
do
some
metrics
and
assessments
of
what
we
are
using,,
we
do
not
realize
that
the
number
of
transactions
or
the
granularity
or
the
pattern
to
be
used,
do
not
allow
them
to
be
microservices,.
Two
very
important
previous
commercials..
The
first
one
is
just
like
they
are
not
going
to
forget
me:
I
did
not
fix
and
so
that
it's
not
free,
free,,
it's
false
no,.
Please
don't
follow
us
with
that,
questions.
Keep
coming
to
me.
B
Many
of
us
said,
hey,,
you
know
that
the
monolithic
ones,
I
don't
bring
a
board,
I
told
them,
hey,,
because
we
don't
want
a
monolithic
one,
and
they
almost
took
me
out
like
that
and
I.
They
turn
my
feet
and
burn
me
in
green
firewood.
They
don't
say
how?
Dare
you
even
mention
the
word
monolithic
in
a
new
application,
and
it
is
that
in
the
end
they
say
well,
we
went
from
what
would
be
monolithic
to
microservices.
B
This
is
older,
but
sometimes
to
see
what
is
happening
and
I
like
the
images.
A
lot
you
go
from
that
great
conglomerate
building
of
apartments,
where
the
departments
are
the
functions
and
from
r
Until
the
parts
to
generate
services
and
that
these
services
arrive
all
connected,,
related,
dependent,,
and
you
realize
that
the
image
on
the
right
side-
remains,,
no,
where
through
that
and
you
generate
microservices,,
you
have
there,
like,,
all
the
functions
you
need,,
but
from
afar.
You
will
realize
that
you
really
have
something
very
similar
to
the
previous
one.
B
That
is
more
manageable,
more
manageable,
as
we
are
going
to
see
now.
However,
well
it
always
has
the
same
roots
and
has
even
greater
complexities,
not
what
is
a
micro
service
for
one
A,
very
joking
definition,
where
it
said
that
a
micro
service
is
a
very
small
function,
so
small,
so
small
that
it
is
a
micro,.
Obviously
it
is
not
a
joke,
because
there
are
many
people
who
do
not
know
how
to
define
what
a
micro
service
is,
no,.
B
So
we
can
say,
for
example.,
which
is
a
programmatic
function
that
is
designed
to
function
independently
and
which
fulfills
one
and
only
one
function
n
within
the
computer
system,
which
computer
system
there
are
other
functions,
the
same
as
them,
and
the
amount
of
this
of
these
services
is
a
certain
number.
The
function
can
be
shared.
You
can
linked
dependent.
That
is
irrelevant.
It
may
be
that
you
have
a
computer
system
where
you
Combine
the
different
microservices
with
monolithic
services
and
some
other
architectural
patterns.
B
Let's.
Remember
that,
thanks
to
the
PSOE,,
which
is
this
service-oriented
architecture,,
which
is
not
a
new
concept
that
many
people
have
made
and
shared
with
them
that
we
were
selling
now
since
2003,
a
4
where
there
was
different
software,
where
we
were
working
on
how
we
were
going
to
divide
all
those
really
monolithic,
monolithic
architectures,
because
we
are
talking
about
the
fact
that
systems
400
mainframes
ago
did
not
leave
the
market
yet
and
if
they
were
still
very
strong,
then
we
were
looking
for
how
to
split
this
type
of
robust
applications.
B
The
huge
heavy
loads
on
different
services,
that
is,
the
psoe
is
a
work
framework
to
be
able
to
divide
these
capabilities
into
different
services,.
Obviously,
an
adaptation
of
this
area,.
Well
now
it
is
definitely
generating
microservices,
because
that
programmatic
function
that
you
divided
and
what
it
did
is
into
monolithic,
generating
different
en
points
and
what
you
were
doing
these
days,
is,
well,,
generating
different
exposures.
Perhaps.
The
sin
was
that,
through
the
same
en
point,
you
had
several
functions
or
several
questions
to
solve,.
B
So
now
you
can
divide
them
much
more
and
be
able
to
achieve
an
architecture
where
you
have
the
services
and
that
perhaps
where,
before
there
was
only
one
pillar,
and
that
this
pillar
undoubtedly
gave
you
a
mechanism
to
be
able
to
expose
all
the
services.
Now
you
have
different
pillars
and
in
these
pillars
you
are
generating.
It
is
very
important
not
to
lose
seen
what
we
have
at
the
bottom,,
which
is
one
of
the
data,,
not
Orita.
B
We
are
going
to
see
a
little
bit
of
its
requirements
a
little
bit
as
we
should
and
implement
a
structure
so
that
the
architecture
based
on
dysfunctions
is
not
because
the
microservices
is
not
the
function
itself.
It
is
all
its
architecture
that
is
related
not
to
Asia
with
what
it
leads
to
It
is
not
a
microservice,.
We
are
going
to
start
by
denying
what
it
is
not
because
sometimes
it
is
much
easier
to
understand
when
we
know
what
a
rest
service
is.
Not.
B
I
have
come
to
different
companies,
and
they
tell
me
we
have
microservices,
hey,
cool
and
how
do
they
implement
them??
We
have
a
set
of
time
insn
rest
and
where
is
the
rest
where
balance
or
discovery?
Where
is
the
scam
breaker?
Where
are
the
failovers
and
logins
everything
that
involves
an
architecture
of
other
services?
We
don't
have
that
today
is
good.
You
are
implementing
it.
No,
no,
no
I
do
n't,
understand
half
of
what
you're
telling
me.
B
I
have
a
load,
balancer
and
I
have
other
things,
but
then
the
implement
a
network
service
or
itself
in
a
microservice.
A
false
idea
that
we
now
have
about
services
is
that
they
say:
no,
if
you
are
not
implementing
networks.
Nine
microservices,,
of
course,
not,
that
is,
we
can
generate
microservices
by
exposing
anything
by
exposing
their
app
or
even
exposing
them
there.
There
is
one
in
a
body
and
for
another
day
where
I
did
an
architecture
based
on
microservices
through
dealing
through
pure
events,
forgiveness
using
ravich,
for
example
friend.
So
you
say
how
is
that?
B
Yes,
because
in
the
end
the
exposure
of
microservices
was
done
through
a
subscription,
because
you
consumed
the
subscription,
and
this
subscription
is
the
one
that
was
exposed
in
the
function,,
so
keep
an
eye
on
the
Rs,.
It
does
not
mean
that
you
are
doing
res
microservices,.
It
is
one
of
the
mechanisms
by
which
you
can
expose
them
in
points
that
your
microservices
have,,
however,
res
by
itself,
is
not
having
microservices
hey
note
that
I
have
microservices,
because
I
deploy
things
in
a
container
He
doesn't
hear
using
what,
by
definition
is
microservices.
B
I
can
support
a
super
heavy
and
badly
done
super
monolithic
platform
in
a
container,
and
that
doesn't
mean
that
I
have
it
good,
but
I
have
it
because
I
haven't
orchestrated
it
by
some
orchestrator
known
to
the
government
that
I
don't
know
of
any
good
provider,
but
they
don't
give
it
to
you.
Either.
It's,
really,
the
principle
that
you
use
to
be
able
to
teach
and
be
able
to
use
it.,
Hey,
I,
don't
know,,
I
haven't
told
you
correctly,.
What
happens
is
that
I
also
have
severe
leds
in
the
key,?
B
Well,
in
my
case,
the
rest,.
The
server
is
a
very
agnostic
way
of
being
able
to
publish
microservices,
however,.
It
saves
them
because
it
not
only
defines
a
microservice,
many
times.
The
server
function
is
used
for
internal
consumption
for
internal
dependencies
to
be
able
to
answer
some
questions
based
not
on
microservices,,
so
it
is
not
a
It
is
a
necessity
for
the
guys,,
even
a
characteristic
of
their
own,
that
I
know
how
to
make
them
see,
you
do
n't
hear,,
well,,
no,,
well,
I'll,
give
it
to
you
if
it
says.
B
I
know
that
by
publishing
in
networks
or
in
a
container
or
in
some
trees,
a
cloud
2
is
that
it
is
not
a
micro
service
by
definition,
it
is
not,.
It
depends
on
how
it
is
built,
not
on
a
bus,
or
it
is
not
the
best
either
because
in
the
end,
a
bus
well
It
is
going
to
help
us
to
make
some
features
that
contain
the
architecture
of
our
services,
however,.
B
It
is
not
the
architecture
per
se,
I,
don't
hear,
I
know,
I
bought
the
domain
driven
design
paradigm
and
therefore,
if
I
build
microservices,
well,
no,,
the
answer
is
out.
There.
One
of
the
most
efficient
ways
to
implement
a
domain-based
design
is
through
the
implementation
of
microservices,
because
in
the
end
the
dead
man
finds
his
defined
patterns,
entities,
objects,
your
services,.
C
B
The
This
is
the
best
way
to
implement
them
through
a
microservices
mechanism
but,
for
example,.
You
can
implement
them
through
events
or
you
could
even
generate
multiple
applications
that
do
not
fall
into
the
concept
of
microservices,
and
you
are
implementing
this
west
vaughn
separation
of
context
about
the
domains
that
your
business
model
can
have.
Then
it
is
not
a
definition
either.
B
Then
they
are
not
by
themselves.
They
are
not
through
any
deployment
or
exposure
or
design
mechanisms.
We
can
generate
the
then
that
my
web
microservices
must
have
so
that
you
are
an
economical
cost
services.
You
must
have
small
full
pins.
That
is
really
your
services
to
start
up
with
little
memory
must
require.
B
The
context
where,
in
this
case,
the
business
is
divided
into
different,
obvious
services
and
you
can
tell
them
you
can
continue
to
be
exposing
no,
but
you
must
have
connectivity.
You
must
expose
a
single
interface.
There
are
no
shared
interfaces.
There
are
not
added
interfaces.
You
must
have
any
very
basic
definition
where,
as
I
ask
the
question
as
the
answer
and
what
is
expected
and
unexpected,
both
in
response
and
in
exception,
obviously
it
can
be
of
local
or
external
consumption.
This
does
not
really
define
any
characteristics
in
this
regard
of
exposure.
B
Should
response
be
responsible
for
managing
your
data
here
here,
but
it
should
be
totally
independent
in
its
administration,
which
means
that
we
should
have
the
independence
to
start
building
a
micro
service
until
its
deployment
should
not
be
interfered
with
by
any
other
service.
Another
feature
hey
wait
because
you
can't
deploy
because
the
other
one
is
here,
notice
that
you
need
to
merge
from
another
branch
or
something
else,
because
you
are
waiting,
not
to
really
see
that
I
am
fulfilling
our
service,
as
a
requirement.
B
You
must
be
totally
independent
in
your
administration,
and
now
you
must
be
responsible
for
managing
your
own
data.
What
does
this
mean?
This
is
a
great
challenge
that
few
very
few
meet
that
I
cannot
have
a
database
that
shares
several
microservices,
because
then
I
am
violating
some
main
characteristics.
No,
so
what
do
I
have
to
do?
B
B
What
happens
when
I
need
to
have
the
most
acidic
transaction
possible?
Remember
these
basic
acid
concepts,
etc.
what
do
I
need
to
do,
because
you
need
to
have
many
problems,
because,
while
having
many
solutions
to
these
problems,
because
how
are
you
going
to
relate
a
set
of
services
that
do
not
depend
on
each
other
that
are
cohesive
with
itself,
but
not
with
the
others
that
are
decoupled?
That
is
only
exposed
in
one
interface
and
that
has
its
own
distributed
data.
B
What
happens
at
the
transactional
moment?
What
happens
at
the
moment
when
we
suddenly
have
to
do
a
bank
transaction
that
the
most
common
thing
we
can
think
of
is
a
subject
of
an
acid
transaction?
Well,
then,
I
have
to
grab
and
I
have
to
do
some
things
like
some.
Even
some
species
of
what
I
have
to
do,
some
sharing
to
use
some
superior
cache
and
guess
what
happens
if
you
make
a
bigger
exhibition
of
all
this
type
of
thing?
B
Sometimes
what
you
will
see
there
is
a
monolithic
and
then
the
question
is:
if
what
I
really
need?
What
I
really
want
is
to
have
that
scheme?
Think
well,
that's
where
I
told
you
at
the
beginning,
that
is,
not
everything,,
not
necessarily
the
monolithic
has
died,
that
is,
really,
on
occasions,
you
will
see
certain
characteristics
where
we
can
or
should
preserve.
B
This
need
to
have
something
that
looks
like
a
monolithic
eye
that
does
have
a
development
cycle
that
does
have
any
characteristics
that
allow
us
to
divide
and
separate
the
councils
separate
the
development
processes,
etcetera
is
correct,
but
the
independent
management
of
the
data
is
a
great
challenge,.
How
do
you
add
or
how
to
synchronize
the
data,
and
how
do
you
make
a
transaction
and
there
they
are
going
to
leave
a
little
homework
and
they
want
them.
We
can
discuss
why,
because
it
is
a
real
challenge.
B
It
is
something
that
when
they
realize
what
they
are
building
are
an
endless
number
of
small
services
exposed
through
a
monolithic,
because
behind
everything
is
one,
it
is
a
database.
It
is
a
single
transaction,
it
is
a
single
validation
mechanism,
etc.
It
is
not
that
Jorge
is
wrong
because
you
have
to
consume
the
other
services.
Yes,
but
the
diagram
starts
to
get
complicated.
Then
the
breaker
cycles
to
break
certain
cascades
start
to
get
too
complicated.
B
So
you
have
to
watch
out
that
we
should
have
something
like
that,
because
part
independence
and
part
microservices
your
residence
fails.
Then
what
do
we
see
with
this?
If
we
already
see
what
is
not
a
micro
service
by
definition,
pu
Whether
or
not
using
a
technology
or
using
a
platform
or
using
a
framework,
defines
us
that
I'm
staying
microservice
mom
goes
further.
It's
a
design
concept,
it's
an
architectural
concept
and
these
requirements,
and
so
I
would
ask
them
not
for
us
to
use
microservices
justifying
Why.
B
Why
did
he
design
it
like
that,
because
it
looks
like
that,
no,
and
whoever
makes
a
mistake
until
what
will
happen,
then
we
will
return
to
the
monolithic
because
we
have
never
left.
It
is
like
when
they
say
that
the
dinosaurs
died.
We
go
to
the
south
of
our
country
in
Mexico
and
you
find
each
each
this,
each
prehistoric,
animal
there.
Yes,
and
this
one,
the
alligators
that
different
iguanas
and
endless
animals-
and
you
tell
them
this
one-
has
more
of
a
godly
face
now
than
me.
B
So
it's
the
same,
the
monolithic
ones
have
not
disappeared.
Nothing
is
clear
and
dark.
You
don't
want
to
go
that
it
will
never
exist
again.
It's
as
if
we
were
saying
that,
like
the
day
you
died,
I
ask
you
how
it
is
like
the
time
I
think
you
should
check
ar
some
architecture
concepts
when
they
say
it
is
that
we
are
not
going
to
use
them
anymore.
It
is
not.
We
should
not
use
them
anymore.
B
It
is
now
we
have
another
alternative,
another
alternative
of
how
to
build
a
system
where
even
development
is
involved,
and
then
they
do
not
begin
to
implement
or
promise
the
implementation,
because
it
is
what
I
have
to
do.
Unfortunately,
many
consultants,
some
companies
sell
the
construction
of
microservices
because
it
is
what
the
other
company
wants.
The
client
has
been
doing
for
a
long
time
with
everything
we
can
travel,
because
it
has
been
strong
for
a
while,
of
course,
you
know
pandemic.
B
B
There
are
many
of
the
people
within
the
media
who
wake
up
today
and
who
say
that
next
Tuesday
with
the
next
one
that
the
company
burns
the
following
year
is
the
company
is
going
to
become
more
technical
to
convert
to
microservices.
If
we
are
a
startup
that
has
an
application
with
ten
screens,
it
conquers
25
use
cases
of
our
application
etc.
well.
Surely
we
can
easily
achieve
it
by
imagining
a
company
like
this
caliber,
where
we
are
doing
different
different
functionalities.
We
have
40
different
products,
etcetera
getting
to
that
one.
B
Well,
no,
because,
depending
on
the
problem,
it
is
the
correct
solution.
Obviously,
if
there
are
mechanisms
to
be
able
to
do
it,
I
understand
that
there
is
a
renewal
issue.
I
understand
that
there
is
an
issue
of
removing
the
obsolescence,
but
the
monolithic
is
not
an
obsolete
pattern.
It
is
a
pattern
that
is
being
left
behind
sar
in
most
cases,
but
it
is
not
obsolete
than
to
say
that
it
is
valid.
So
what
do
I
have
to
watch
out
for
when
I
am
trying
to
implement?
Now
it
is
a
microservices
architect.
B
If
it
is
a
culture,
it
is
a
culture
that
we
should
not
lose
sight
of,
that
the
The
term
was
coined
more
than
10
years.
Ago,
yes,
and
this
term
has
evolved.
This
term
was
coined
almost
when
it
was
hatching,,
and
there
obviously
are
great
representatives
who
have
handled
it
and
probably
accompanied
by
the
divine
of
this
friend
Eric
Vance,
who
used
it.
It,
promoted
a
lot,
and
it's
good
that
they
are
activity
leaders
because
it
has
spread,.
So
what
does
the
architecture
of
many
services?
Allow
me
to
enable
a
fast,,
frequent
and
reliable
way?
B
Yes,
deploy
different
applications
based
on
modern
technologies?
That
allows
me
to
have
a
development
life
cycle.
very
optimal,
because
because
it
allows
me
to
separate
the
teams,
it
allows
me
to
control
their
deployment.
It
allows
me
to
avoid
g
large
and
heavy
deployments-
note
large
and
heavy
deployments.
Normally.
The
deployment
pipelines
can
take
many
minutes
in
many
minutes,
because
sometimes
you
have
to
download
the
internet
to
compile
something
or
you
have
to
do
something
special
there
that
makes
techniques
and
optimizations,
but
most
don't
either.
B
Architecture,
what
challenges
do
they
overcome
location
I
have
to
be
able
to
locate
the
services
that
I
need
to
expose
efficiently
in
order
to
have
high
availability,
what
it
does
in
case
of
failure,
even
in
case
of
no
failure.
Remember
the
principle
of
rest
that
allowed
us
to
locate
the
services
consecutive
through
of
the
same
answer.
Then
it
is
a
is
a
is
a
ma
The
way
to
do.
It
has
to
have
a
true
resilience,
that
is,,
it
has
a
true
fault.
B
Tolerance,
I
must
have
the
ability
to
be
able
to
recover
automatically
in
a
systematic
way
and
that
this,
and
that
this
does
not
lead
to
a
great
snowball-style
disaster
or
something
that
looks
like
it
should
not
have
a
configuration
management
capacity,.
What
does
this
mean
that
it
should
be
able
to
have
a
central
configuration
when
we
are
talking
about
a
complex
architecture,,
since
we
have
several
dozen
exposed
microservices
fulfilling
different
use,
cases,
among
them
all
derived
from
some
cases
of
very
specific
business?
B
B
How
do
I
tell
someone
that
something
happened
and
that
I
have
to
find
out
where
the
problem
was
where
there
was
the
instruction
where
there
was
security
eloy,
where
there
was
the
programmatic
error,
then
obviously
I
have
to
have
a
deployment
management,
as
it
is
the
mechanism
that
they
are
doing
a
lot
to
you.
They
are
thinking
that
the
cloud
solves
it
well
if
the
Amaya
can
solve
cases
with
different
services
and
different
mechanisms,,
including
different
software,,
but
neither
all
slaves
nor
everything
solves
magically..
B
We
have
to
keep
this
very
in
mind
and
obviously
security,
that
is,
security
is
something
extremely
important.
Yes,
ensuring
a
monolithic
was
complex,,
because
now
it
ensures
hundreds
of
services,
because
it
is
more
because
but
well
we
use
one
with
the
authentication
server
with
an
api
get
away
to
be
able
to
validate
each
of
the
calls
from
the
shapis
that
you
have
etc.
yes,
it
can
be,
but
remember
that
doing
this
introduces
points
single
points
of
failure
and
the
single
points
of
failure
then
gives
us
a
problem
that
is
su.
B
B
So
what
should
we
or
what
should
we
typically
do?
We
have
to
have
a
configuration
service
in
the
past.
Rius
from
netflix
was
used
a
lot.
Not
many
of
these
technologies
have
been
taken
over
by
spring
cloud
to
be
able
to
do
it
and
in
jakarta
we
use
it
a
lot.
What
is
the
problem
that
some
of
these
are
already
in
maintenance
mode?
They
have
been
replaced
by
other
software
For
other
implementations,
and
they
even
recommend
that,
if
you
don't
use
something
already
very
stable
in
a
cloud,,
then
implement
it.
There
is.
A
B
Alternative
for
arcades
for
Netflix
and
Mac,
only
that
it
is
quite
accessible.
We
have
to
have
a
discovery
service
to
be
able
to
find
this
amount
of
services
that
are
exposed
and
preferred
by
all
is
European
and
ureka.
Sorry,
because
it
works
quite
well
with
riva
to
be
able
to
do
the
balancing
in
an
integral
way,.
However,
ribó.
C
B
Already
passed,,
the
project
has
been
under
maintenance
for
a
couple
of
years,
so
they
are
no
longer
dedicating
effort
to
this
to
these
projects.
So
You
have
to
look
for
alternatives
and
there
is
more
software
and
there
are
more
frameworks,.
They
have
taken
care
of
me
please,.
It
is
not
something
that
is
simply
teaching,
but
the
feature
obviously
has
to
exist,.
He
is
so
famous
and
the
baker
to
be
able
to
do
it,
the
one
we
use
a
lot
because
it
is
high
street
on
street.
However,
you
want
to
pronounce
it
from
netflix.
B
The
truth
is
that
I
also
work
called
maintenance
for
almost
three
years
now.
This
is
no
longer
an
alternative
if
we
want
to
get
away
from
obsolescence,
but
there
are
other
projects
there
is
rising.
For
gay,
there
is
sentinel
where
they
are
inherited
from
the
previous
project
and
without
maintenance,
and
it
is
an
alternative
for
you
to
use.
Obviously,
we
need
to
have
a
services
To
be
able
to
put
a
front.
B
We
can
use
anything
in
the
cloud
that
this
border
service
can
offer
us,
but
hey
if
we
can't
use
blue,,
which
also
involved
a
lot
of
maintenance,
well,,
also
red
in
the
presentation,,
but
but
the
new
ones,.
The
new
proposals
are
low
in
net
and
even
the
entire
netflix
open
source
scheme
suggests
by
itself
the
use
of
medo.
And
finally,
we
bet
that
using
log
management
and
I
actually
used
greylock.
It
is
quite
interesting.
It
is
easy
to
use
and
allows
you
to
concentrate.
B
Do
problems
as
long
as
the
tool
is
not
as
designed,
so
if,
within
your
events,
it
does
not
have
a
format-
and
you
do
not
have
some
mechanism
to
be
able
to
carry
out
these
correlations,,
then
really
that
you
use
to
concentrate
the
blogs
is
nothing
more
than
inefficient
here.
I'm
going
to,
let
us
share
it
with
you,,
it
can
only
be
seen
in
the
video,.
That's
fine,
I
can
share
it
with
you.
B
the
presentation
and
well
as
more
or
less
some
other
software
alternatives
that
can
be
used
to
fulfill
this
orchestration
mechanism
to
be
able
to
make
the
exposure
and
the
different
characteristics
of
configuration
of
discovery,
not
of
the
characteristics
of
the
monitoring
that
is
had
for
an
observability
the
issue
of
late
service
through
routing
etc.,
and
this
is
one
of
the
characteristics
that
can
be
found
in
some
typical
architectures,
and
we
can
do
it.
I
insist.
The
tools
are
very
important.
B
So
why?
Because
it
is
not
the
general
objective
micro
service
is
not
just
a
architecture.
Pattern
is
a
set
of
patterns
6
about
36
patterns
that
we
should
typically
use
as
we
are
implementing
microservices.
Why?
Because
we
have
to
implement
events,
we
have
to
implement
observers.
We
have
to
have
different
adapters.
We
have
to
have
various
expectations
of
how
how
to
isolate
handling
of
the
objects,
OS
and
services
within
a
separate
context
design.
B
We
also
need
to
handle
some
aspect:
oriented
orientation
to
be
able
to
generate
layers
of
volatility,
to
be
able
to
generate
more
consistent
security
layers,
whether
you
implement
them
or
whether
you
use
some
triangle
to
do
it.
No,
then
We
already
have
some
anti-patterns
out
there,,
so
something
that
I
really
like
to
remind
you
of
when
I
talk
about
microservices
architecture
is
very
important,.
Is
that
you
don't
forget
Conway's
law
for
those
who
don't
find
it
quickly.
B
Normally,
if
your
structure
is
in
a
mess
from
developing
software
in
a
mess,
because
because
the
business
models
and
communication
models
that
your
company
has
organization
are
affected
in
the
way
that
Design
simply
like
this,
try
these
services,.
So
if
you
want
to
implement
microservices,-
but
here
you
also
have
to
see
that
if
your
company
has
a
structure
that
promotes
them,
the
typical
example
of
the
company
that
you
do
not
create
and
well,
at
least
in
Latin
America
continues.
B
But
very
many
is
the
one
who
takes
the
vision,
the
director
of
the
company,
who
is
normally
the
found
you
are
the
owner
and
the
one
who
gave
everything
typical.
Then
there
is
a
person
who
has
a
vision
of
everything
that
happens,
begins
to
complicate
the
concept
of
microservices.
Then
we
will
begin
to
say:
hey
I
will
be
able
to
achieve
it
if
I
cannot
achieve
vertical
centuries
in
business
areas
within
the
organization.
How
am
I
going
to
divide
my
domains?
How
am
I
going
to
be
able
to
identify
these
entities
that
meet
certain
true?
B
This
value
object
as
a
pattern
implementing
them,
as
services
is
going
to
be
very
complex,,
so
it
is
very
important
to
look
back
a
little
rec
Remember
that,
for
example,,
when
accounting
is
no
longer
necessary
or
is
not
enough,
and
that
the
organization
has
an
agile,
IT
area,.
The
organization
itself
has
to
be
an
organization
of
self-knowledge,
of
maturing
growth
to
be
an
agile
organization,
if
not
It
doesn't
work
in
the
same
way.
B
If
your
organization
looks
like
a
monolithic,
it
looks
like
a
disaster,,
it's
hardly
going
to
be
able
to
generate
correct
microservices,
and
it's
not
that
it
failed
in
the
design,.
I
swear
it's
common,,
it's
something
inherent
to
the
process
that
suddenly
generates
different
knowledge,
different
design,
and
you
are
realizing
that
what
happens
is
that
the
problem
is
the
organization
per
se.
B
If
two
areas
cannot
communicate
if
two
areas
cannot
make
the
decision
on
the
separation
of
responsibilities,
if
two
areas
cannot
speak
the
same
language
as
thinking
a
little
divided
about
that,
there
should
not
be
dominance.
This
pardon
should
not
be
the
language
or
of
ambiguous
in
the
way
of
expressing
yourself,
well,.
As
we
are
going
to
do
it,,
then
it
is
very
important
that
you
in
architecture
consider
that
this
is
happening,
hey,.
What's
up
with
Jakarta
?,
they
all
tell
me
it's
not
that
with
jakarta.
We
can't
do
it
because
the
technology
is
old,
well,.
B
How
old,
if
we
just
released
and
based
on
we
just
released
it
comes
17.
The
letter
of
10
is
coming
for
the
next
year.
Technology
room
has
a
lot
of
time.
If
you
have
a
lot,
you
can
having.
Some
component
is
legal.
If
you
can
have
a
technical
debt
like
anything
else,
however,
technology
has
been
adapting,.
We
have
been
generating
certain
adaptations
for
this
to
happen,
no,,
then
the
pretext
that
the
technology
is
old
is
totally
unrealistic,.
We
can
build
with
keys
without
any
problem.
B
Everyone
at
the
microservices
say
today
is
that
it
is
not
stable,
as
it
will
not
be
stable.
A
gr
A
percentage
of
the
internet
and
current
applications
run
on
flame,
or
is
it
that
they
are
changing
a
lot
since
we
have
not
changed
that
much.
In
fact,
there
are
people
who
complain
that
the
evolution
of
language,
different
technologies
and
others
have
slowed
down.
Well,
yes,
we
already
know
that
this
migration
that
we
had
after
passing
from
it,
it
goes
towards
the
letter
of
work,.
B
That
It
is
much
more
stable
than
ever,
and
it
has
always
been
as
clear
as
any
framework
or
quantity
and
set
of
technology
because
it
has
its
challenges,
I,
don't
know,
it
's
nothing.
Obvious.
You
saw
the
maintenance
of
this
number
of
projects,,
so
it's
not
fast,
Chávez,
fast,
many
times,.
If
it's
not
fast,,
it's
our
fault,
due
to
the
number
of
frameworks,
latency
layers,
that
we
can
include
in
the
software,
or
the
bad
programming
that
we
do,
there's
always
a
mechanism
that
doesn't
work
for
you..
B
Cheeks
are
scared
and
everyone
is
afraid
of
using
things
in
memory
or
bringing
things
closer
to
reduce
latency
the
6
that
they
generate
only
a
monolithic
did
not
bring
them
closer
that
sometimes
separating
two
components
can
generate
too
much
latency
the
most
expensive
thing
in
the
computing
is
the
existence,
or
not
only
of
the
physical
part
of
the
hardware,
but
also
through
the
networks.
So
remember
that
now
that,
and
especially
those
who
love
the
cloud,
the
virtualized
iverson
cloud
on
virtualized
hardware,
then
the
steps
between
different
layers
are
very
wide
and
very
high.
B
B
Because
because
we're
very
much
married
to
an
old
way
of
doing,
it,,
I've
recently
faced
a
Harlingen
process.
We
mentioned
it
here
on
ski
and
this
one
and
I
find
that
there
is
many
people
who
stayed
in
the
past
and
who
need
to
update
themselves
on
how
to
build
know
how
to
build
pipelines,
how
to
have
integrated
quality,
that
is,
unit
testing
is
no
longer
the
only
thing
that
works
that
should
do
comprehensive
tests
performance
tests.
B
That
We
must
think
a
lot
about
the
way
in
which
the
function
is
exposed
and
the
patterns
that
we
are
placing
behind
one
component
and
another
so
that
all
these
characteristics
are
generated..
I
do
believe
that
it
is
somewhat
right,
however,
to
adapt
and
learn
it,
and
that
is
something
simple,
and
we
also
have
a
lot
of
people
out
there
who
are
developing
in
key,
and
they
say
that
architectures
cannot
be
achieved
with
key
and
n
a
way
of
a
king
code
or
a
clean
architecture.
B
So,
let's
not
forget
that
jakarta
has
long
before
its
definition
of
version
8
of
jakarta,,
which
is
where
it
was
the
transition
all
the
sufficient
technologies
to
be
able
to
implement
our
services.
We
have
all
the
specification
of
multiplication
networks
of
your
app.
We
have
the
specification
for
database
access.
We
have
a
different
pattern
of
architecture
connectivity
on
the
16th.
We
have
not
worked
and
we
have
suffered
this.
This
evolution
of
perhaps
seeing
their
ideas
and
that
sometimes
we
screw
up
It
is.
B
Sometimes
it
gets
a
little
confused
and
is
handled
thinking
that
this
is
only
the
jason
web
token.
Well,
we
also
have
a
protocol
and
the
web
touches
so
well.
Well,
we
have
mechanisms
to
be
able
to
ensure
all
times,
and
the
statistics
are
cryptography.
We
can
handle
the
current
public
keys.
That
is
not
an
issue
I.
Have
we
have
there?
No,
what
is
the
challenge?
The
challenge
is
that
you
use
modularity
d
to
reduce
the
size
of
the
tree,.
B
The
fact
is
that
you
have
a
minimum
number
of
libraries
to
add
to
your
save
file
to
be
able
to
generate
this,.
So
that
is
the
real
challenge
that
you
can
use
a
modularity
that
has
already
been
based
on
java
modules,
or
even
that
you
do
it
through
your
architectural
design
and
that
you
can
deliver
a
very
tiny
guard
that
is
deployed
like
this.
Why?
Because
exactly
what
has
become
a
problem?
The
number
of
instances
that
we
have,
how
we
distribute
them,
how
we
publish
it
that
is
stable?
Well
org!
B
There
are
many
solutions,
that
is,
you
can
generate
images
of
containers,
download
some
official
public
image
of
some
containers
that
exist
with
an
application
server
with
any
of
the
flavors
that
we
friends
from
the
world
of
ibm
who
are
out
here,
have,
well,.
They
have
different
alternatives
and
obviously
Well,
you
have
to
put
it
in
containers
to
be
able
to
make
an
efficient,
rapid
deployment,.
Perhaps
a
Such.
An
important
issue
is
disk.
Memory.
B
The
start
of
time
is
still
an
issue,
of
course,
because
we
expect
microservices
to
take
seconds
or
a
couple
of
seconds
maximum,
and
that
is
already
a
lot
and
the
little
traditional
beings
that
will
be
a
little
longer
will
not,
however,.
If
you
plan
wind
deployments
and
you
have
good
control
of
the
changes
and
the
way
of
automating
this
deployment
plan,,
you
can
solve
it
without
so
much
problem.
The
memory
of
the
disk,,
since
it
is
that
much
disk
you
can
use,,
it
will
depend
on
your
design,.
You
should
not
be
throwing
a
local
disk.
B
This
is
not
a
problem
and
the
memory,.
Well,
sometimes
you
have
to
make
the
decision
if
your
application
server
consumes
a
lot
of
memory
or
divides
it,
and
if
it
is
a
micro
service,
it
is
very
small.
It
should
not
also
make
a
theme
you
can
put
a
very
small
content
displayed
in
a
very
very
small
instance
and
generate
many
of
them.
Remember
that
here
the
idea
is
to
use
power
as
a
distributed
whole
or
match
even
with
this
virtualization.
B
No,
so
it's
a
matter
for
those
of
micro,
please
I,
know
I,
better,
say
good,
but
I
missed
one,
and
this
is
a
way
to
do
now.
Also,
the
services
remember
that
micro
profile
is
not
an
option.
Sometimes
it
is
It.
Has
this
misconception.
It
is
one
more
way
of
using
java
this.
There
are
different
talks.
Discussions
about
the
merger
into
one
micro
by
falcón,
jakarta
of
some
simple
ones
say
that
I
have
not
really
advanced
the
micro
profile.
This
way
to
implement
a
cloud
gate
and
architecture
is
It
really.
B
Is
the
origin,
not
really
to
use
the
issue
of
implementation
in
the
services,?
Its
technologies
will
be,
well,.
It
is
already
accessed
by
Jacques,.
This
is
an
idea
and
Jason
Pino
for
everything
we
have,
so
I
think
that
anyone
who
knows
already
loads
and
can
use
it.
because
it
is
the
same
java
technologies
and
you
can
use
any
of
them.
We
do
not
go
back
to
the
same
use
your
containers
and
deploy
them,,
which
is
what
ue
comes
in
the
time
of
jakarta
and
because
time
is
running
out
because
important
things
are
coming.
B
So
we
see
four
skip
four
alternatives.
We
do
not
use
jakarta
with
and
without
an
answer
be
aware
that
it
is
not
always
necessary
to
put
a
container
in
and
with
a
compromising
deployment
and
a
clown
or
there
they
need
what
they
have,
because
they
can
do
both.
They
can
not
also
use,
for
example,
micro
profile
with
and
with
termination.
I
think
it
is
an
alternative,
not
in
deployment
of
cloud
programming.
If
the
vendors
of
micro
by
file
already
have
several
images
already
public
and
stable,
only
you
can
use
an
alternative.
B
Spring
cloud
has
been
moving
after
this
depredation.
That
told
you
about
the
netflix
or
ss
components
that
you
had
then
through
spring
boots,
a
very
interesting
whole
being
and
for
those
who
are
always
looking
for
something
new,
because
we
have
rooms,
not
rooms
of
reality
and
how
good
it
is
obviously
created
for
your
sprint
vernet
and
this
one
and
offers
dif
erent
very
interesting
characteristics
to
be
able
to
generate
this
deployment
super
fast
and
everything
is
very,,
very
small.
B
So
we
currently
have
four
aspects,
everything
is
based
on
java
and
jakarta,
and
in
the
end,
well,
we
have
different
alternatives,.
The
jakarta
vibration
of
10
comes
for
him
with
one
from
2022
and
then,
well,.
It
would
be
interesting,,
so
don't
stop
seeing
what
the
new
things
are,
new
updates
to
the
apis
are
coming,.
They
have
super
stabilization,.
There
was
no
big
problem
with
the
migration
of
the
main
package
from
it,.
It
is
already
going
to
Jakarta,
and
this
one
and
the
different
technologies
are
evolving.
B
So
the
conclusion
is
to
make
unique
services
when
we
are
balancing
the
architects
that
are
required
to
build
applications
based
on
a
good
separation
of
domains
in
new
analysis
of
the
differences,
functionalities
and
cases
that
can
be
done
if
they
go
to
implement
in
which
services
do
it
well,
the
most
as
clean
as
possible,
it
will
not
always
be
possible.
He
is
a
very
titanic
person.
I
do
not
think
that
a
migration
from
a
system
to
a
monolithic
or
service
environment
is
obvious
and
easy.
It
requires
a
lot
of
time
and
a
lot
of
effort.
B
Almost
almost
the
same
team
that
is
working
on
the
creation
of
the
monolithic
must
be
used
for
microservices
or
make
a
migration
quite
slow
to
make
it.
What
you
are
in
jakarta
with
this,
we
can
do
it
in
any
flavor
in
any
of
its
aspects
now
and
we
can
achieve
it
and
do
not
make
microservices
because
before
services
or
let's
not
say
that
we
do
it.
If
we
don't
have
those
minimum
architectural
characteristics,,
they
come
out
well,.
That's
my
participation,
just
finish
fruit,
before,,
sorry,
and
if
there
were
questions,
but
thanks.