►
Description
Presented by Turja Narayan Chaudhuri at the May 20, 2022 Ortelius Visionaries Summit
It is indeed a valid argument that microservices allows engineering organization to grow and scale, providing better constructs for isolation and independence. But, microservices do not only add technical complexity -they also introduce organizational complexity and pose a serious threat to scaling at the enterprise level. Over time, with hundreds of services and no governance or oversight, when something breaks, nobody knows who to reach out to. A microservice catalog is a record/list of all the microservices that an enterprise has in its ecosystem, providing powerful information at your fingertips. In this talk, you will learn how a microservice catalog facilitates a successful microservice at scale architecture by helping developers find and share services, providing DevOps teams metadata about services needed to make solid decisions, and give the support teams the ownership and consumption information needed when something goes wrong.
A
So
a
brief
about
me.
Currently,
I
am
an
assistant
director
cloud
practice
at
ernest
and
young
before
that
I
used
to
lead
the
cloud
center
of
excellence
team
at
accenture.
So
what
is
the
agenda
for
today?
So
this
is
a
10
minute
lightning
talk
where
I
will
discuss
the
challenges
with
current
micro
service
adoption
across
enterprises
at
scale.
What
is
a
micro
service
catalog
how
it
can
act
as
a
solution?
A
77
percent
of
respondents
have
adopted
microservices,
which
is
huge,
and
actually
it
is
agreed
by.
The
industry
thought
leaders
that
enterprises
that
are
not
able
to
effectively
support
micro
services
will
be
able
to
less
compete
in
the
business
in
the
future,
whereas
enterprises
who
have
adopted
micro
services,
they
are
more
likely
to
perform
well
against
others
on
metrics,
like
development
efficiency,
the
ability
to
use
new
platforms,
collaboration
across
teams
and
sharing
of
services
across
applications.
A
So
microservices
is
in
the
market,
and
it
is
the
next
big
thing,
but
at
the
same
time,
the
number
of
micro
services
can
be
insane
over
a
period
of
time
in
an
enterprise.
So
here,
if
you
see
uber
in
2018
and
netflix,
you
can
see
this
is
the
micro
service
graph,
how
many
services
and
how
complex
that
interdependencies
are
so
managing
something
like
this
at
a
enterprise
level.
At
an
enterprise
scale
is
very
difficult,
so
what
are
the
difficulties?
A
So
as
long
as
you
have
5
10,
20
30
micro
services,
it
is
still
ok,
you
can
maintain
them,
but
the
moment
you
have
more
than
30
micro
services.
It
becomes
unmanageable
their
cracks
start
appearing
in
the
system.
Why?
Because
there
is
no
clear
ownership.
Nobody
knows
who
to
contact.
If
that
service
breaks.
There
is
no
easy
way
to
reach
the
consumer
of
a
service
or
to
reach
the
owner
of
a
service.
To
understand
who
is
responsible
for
this
service.
A
There
is
no
easy
way
to
access
documentation
to
get
analytical
information
about
the
microservices
and
all
of
that
and
how
to
consume
it
so,
basically
at
scale.
When
you
have
a
lot
large
number
of
micro
services,
it
becomes
very
difficult
to
manage
it.
What
are
some
of
the
difficulties?
It
is
impossible
for
a
single
person
or
a
team
to
be
aware
of
all
the
micro
services
across
the
enterprise.
Okay,
nobody
can
pinpoint
when
a
service
goes
down,
that
who
is
the
owner
of
the
service?
A
Who
should
I
reach
out
to
get
clarity
on
that
service
which
leads
to
delays?
There
is
a
lack
of
visibility
across
an
enterprise
into
what
is
the
kind
of
micro
service
adoption
state
in
that
enterprise
which
programming
languages
are
being
used,
which
microservice
frameworks
are
being
used,
and
there
is
a
high
degree
of
duplication.
Maybe
you
and
I
both
part
of
the
same
enterprise
are
developing
the
same
microservice
same
service.
We
are
not
even
aware
of
that.
A
So
there
is
a
lot
of
duplication
and
a
lot
of
cost
to
the
company,
because
potential
reusable
opportunities
are
being
missed.
So
overall,
when
a
devil
from
a
developer
perspective.
Also,
when
a
developer
wants
to
develop
a
service,
he
doesn't
know
if
there
is
anything
that
he
can
use
as
a
building
block
to
his
own
service,
because
there
is
no
easy
way
to
get
a
view
of
all
the
services
in
the
enterprise.
A
So,
basically,
whereas
we
wanted
micro
services
to
be
a
catalyst
in
our
digital
transformation
journey,
it
is
actually
becoming
a
kind
of
hampering
our
journey
in
a
sense.
So
it
is
not
only
adding
technical
complexity
which
obviously
microservices
does
at
some
level,
but
they're,
also
introducing
organizational
complexity
and
they're,
posing
a
very
serious
threat
on
how
to
scale
the
enterprise.
A
So
what
is
the
solution?
We
understand
that
these
are
the
challenges
right,
which
makes
sense
whenever
you
are
managing
something
across
five:
ten,
twenty
thirty
forty
five
hundred
five
thousand
fifty
thousand
services
you
need
somewhere,
where
you
can
get
a
unified
view
of
the
services,
and
that
is
where
a
micro
service
catalog
comes
into
play.
It
is
basically
service
discovery,
but
for
humans
it
is
a
record
or
a
list
of
all
the
micro
services
that
an
enterprise
has
running
in
production.
A
What
each
service
does
it
also
contains
metadata
about
the
service
like
owner
of
the
service
service,
now
queue
of
the
service
where
I
can't
find
observability
or
promises
charts
for
that
service?
How
do
I
operate
the
service?
How
do
I
consume
the
service
using
a
catalog?
It
is
very
easy
for
a
developer
who
is
getting
onboarded
to
see?
Okay.
These
are
the
number
of
services
that
I
have.
This
is
my
service.
This
is
how
my
service
is
dependent
on
all
of
these
services,
so
I
should
be
aware
when
these
services
go
down.
A
I
should
design
my
monitoring
accordingly,
I
should
design
my
observability
accordingly
and
it
gives
the
enterprise
leadership
the
executive
board
a
control
over
the
micro
service
adoption
across
the
enterprise
they
can
see.
Okay
today,
30
micro
services
are
there.
In
six
months
we
have
hundred
micro
services.
This
is
a
year
on
year.
A
Growth
of
micro
services
is
the
kind
of
programming
languages
used
by
the
micro
services
and
all
of
the
details
they
can
get
very
easily
so
micro
service
catalog
gives
you
back
that
sense
of
control,
whereas
you
were
earlier
in
a
chaos
with
hundreds
and
thousands
of
services
having
a
micro
service.
Catalog
gets
you
back
that
control
over
your
entire
state
of
the
enterprise,
and
it
helps
your
developers
adopt
the
micro
service
journey
in
a
much
more
agile
way.
A
So
this
is
a
functional
representation
of
how
a
service
catalog
works
at
a
very
high
level.
So
the
service
teams
who
are
publishing
the
services
who
you
can
call
as
service
publisher,
they
will
publish
the
services
onto
the
enterprise
catalog.
This
can
be
automatic
via
auto
search
or
auto
service
discovery
process.
It
can
be
manual.
You
can
upload
some
metadata
and
register
your
service
to
the
micro
service.
Catalog,
a
bad
job
might
be
running
which
will
scan
all
the
services
within
my
organization
at
a
regular
interval.
A
So
many
things
can
happen,
but
at
the
end
of
the
day,
my
service
information
needs
to
be
pushed
or
inputted
into
the
micro
service
catalog
and
the
same
hand.
On
the
other
hand,
the
micro
service
consumers
who
are
consuming
my
micro
services,
they
will
basically
use
this
micro
service
catalog,
which
is
an
enterprise-wide
entity
as
a
single
source
of
truth
for
all
the
services.
In
my
enterprise
they
will
go
there
and
try
to
find
which
services
makes
sense
to
them.
A
So
this
is
kind
of
a
model
which
service
consumers
and
service
publishers
acting
as
a
whole.
Cohesive
group
group,
with
the
benefit
of
this
micro
service,
catalog
and
a
micro
service
catalog,
will
end
up
acting
as
a
single
source
of
truth.
You
can
build
complex
analytics
on
top
of
the
service
catalog.
You
can
answer
questions
like
what
is
the
rate
of
growth
of
micro
services.
In
my
enterprise
over
the
last
6
to
12
months,
some
teams
can
ask
questions
like
what
does
the
service?
I
do.
A
What
are
some
of
the
options?
Some
of
the
very
well
known
options
is
obviously
ortelius,
which
is
an
open
source
project
under
continuous
delivery
foundation.
It
is
a
very
well
known
micro
service.
Catalog,
you
should
go
and
check
it
out.
Also,
deploy
hub
is
also
a
very
good
option,
which
is
an
enterprise
grade
option
that
can
help
you
simplify
all
of
the
same
problems,
tackle
all
of
the
problems
and
much
more
benefits.
A
A
So,
basically,
what
we
are
trying
to
what
I
am
trying
to
portray
here
is
that
there
is
actually
a
very
real
challenge
and
a
very
real
danger
to
the
scaling
of
your
enterprise.
If
you
are
not
able,
if
you
are
not
able
to
have
some
sort
of
a
strategy
behind
it
for
a
few
services,
it
is
okay.
But
the
moment
you
cross
that
threshold
of
30
or
40
services,
it
becomes
very
difficult,
so
you
can
start
small.