►
From YouTube: CDFoundation15MinuteDemo
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
A
A
So,
what's
lost
in
the
microservice
approach?
Well,
the
application
version
schema
goes
away,
and
this
impacts
things
like
testing
and
bug
tracking
and
even
value
stream.
Things
like
something
as
simple
as
as
a
bill
of
material
report
goes
away.
How
is
the
application
configured?
What
is
it
consuming?
What's
difference
between
the
last
time
we
deployed
it
or
what
happened
five
minutes
ago
that
changed
its
the
way
our
application
is
behaving
and
impact
analysis.
When
should
I
release
a
new
microservice?
Who
is
it
going
to
impact
so
key
to
this?
A
Let's
take
a
look
so
for
the
purpose
of
this
demo.
We
are
going
to
take
a
look
at
domains,
applications
and
components.
We'll
start
at
the
domain
domains
are
a
way
to
organize
your
microservices
into
solution
spaces
in
this
demo
in
our
fictitious
company
called
the
online
store
company.
We
have
four
primary
domains.
Two
of
them
the
store
service
and
the
purchase
processing
are
what
we
call
catalog
domains.
A
A
When
you
create
a
base
version,
you
do
this
once
and
you
define
it
in
a
very
similar
way
that
you
might
in
any
release
automation
solution
that
allows
you
to
package
your
application.
Now,
in
this
case,
we
can
see
that
we
have
several
microservices
here,
one
that
includes
the
cart
service.
The
cart
service
has
been
pulled
from
the
purchase
processing
domain,
so
it's
outside
of
the
hipster
store,
they're
borrowing
somebody
else's
microservice.
A
Now
you
also
see
this
there's
a
new
version,
but
they're
using
the
the
original
one.
This
base
version
is
using
the
gc6.
Now,
let's
go
back
and
take
a
look
at
what
happened.
We
have
a
new
version
of
our
hipster
store,
fourth
of
july
cell,
and
if
we
drive
down
into
that,
let's
see
why
what
what
created
this
new
version?
A
A
A
The
card
service
is
a
pretty
important
piece
of
the
overall
puzzle
for
our
online,
our
fictitious
online
store
and
in
fact,
it
impacts
five
different
applications.
So
we
understand
from
a
a
developer,
microservice
developer,
that
when
we
do
implement
a
new
version
of
the
cart
service,
we
we're
going
to
impact
those
five
application
teams.
We
may
want
to
notify
them
that
a
new
version
is
on
the
way.
Now
what
happened?
What
occurred?
We
can
see
that
the
cart
service
was
updated
via
a
circle.
Ci
pipeline
build
number
179,
it
was
registered
with
quay.
A
A
We
can
also
see
where
it's
been
deployed
now.
This
is
a
simple
example,
but
you
can
imagine
if
you
have
multiple
microservices
being
pushed
to
multiple
clusters,
each
version
of
the
microservice
being
being
independent,
they're
immutable.
So
this
allows
you
to
see
where
they've
been
deployed
and
how
they
got
there.
A
So
the
results
of
a
deploy
have
implementation
first
starts
with
taking
the
guesswork
out
of
tracking
who's
consuming
microservices
and
what
your
application
configuration
looks
like
according
to
our
customers,
we're
saving
them
about
three
to
six
hours
of
manual
tracking
work
per
team
each
week.
Secondly,
microservice
sharing
can
really
reduce
redundant
coding.
The
last
thing
you
want
to
do
with
microservices
is
to
have
every
team
write
a
login
routine
by
having
a
centralized
catalog
that
allows
you
to
share
microservices.
You
can
reduce
redundant
coding
by
up
to
50
percent.
A
Flying
blind
can
be
difficult
when
you're
about
to
deploy
a
new,
microservice
and
you're,
not
quite
sure
what
the
impact
is
going
to
be
so
before
you
find
an
incident
and
have
to
track
why
your
microservice
broke.
Something
deploy
hub,
gives
you
some
visibility
and
understanding
how
that
microservice
is
going
to
impact
where
you're
deploying
it
to
so.
We
provide
that
data,
those
the
data
to
make
the
data
driven
decisions
that
your
sres
need
to
not
fly
blind.
A
That
code
is
fixed,
you
get
a
code
complete
status
and
you
update
and
create
a
new
container
that
contains
your
microservice.
At
that
point,
we
now
have
a
release
candidate
and
that's
when
deploy
hub
kicks
in
deploy
hub
then
determines
who
has
been
impacted
by
that
new
container
that
new
microservice
increments.
The
application
version
provides
those
bond
reports,
the
diff
reports
and
the
impact
analysis
reports.
A
It
pulls
the
shaw
the
git
commit
and
the
cr.
So
once
you
deploy
it,
it
starts
tracking.
What's
in
the
clusters,
so
you
may
have
several
clusters
in
your
dev
test
environments:
we're
going
to
track
what
version
of
of
an
applications
in
a
cluster
and
what
versions
of
the
microservices
are
in
those
clusters
and
that's
the
same
with
production.
A
Thank
you
for
taking
the
time
to
learn
a
little
bit
about
deploy
hub
and
how
we're
making
your
microservice
journey
easier.
I'm
always
interested
in
speaking
to
individuals
who
are
working
in
the
microservices
environment.
So
if
you're
interested
in
chatting,
you
can
find
my
calendar
at
deployhub.com.