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 support teams ownership and consumption information needed when something goes wrong.

1. Why do you need a
microservice catalog to
enhance developer
productivity?
Presented by Turja Chaudhuri

2. Introducing Ortelius Open Source
• Ortelius is a microservice catalog that governs your microservice supply chain tracking versions, blast
radius, inventory, SBOMs, CVEs, and the teams that support them providing a proactive view of your
microservice application as it changes over time.
• Ortelius is an incubating project under the governance of the CD. Foundation (Linux Foundation).
• Our mission is to simplify the adoption of microservices through a world-class microservice
management platform driven by a supportive and diverse global open-source community

3. Meet the Presenter
Turja Narayan Chaudhuri
• Currently , I am working as an Assistant Director, Cloud
Practice at EY (Ernst & Young).
• Before that I led the CCOE ( Cloud Centre Of Excellence)
Team at Accenture.
• I Have around 10+ years of IT experience , working on
Public Cloud technologies since 2017.

4. Session Topic
Why do you need a microservice catalog to enhance developer
productivity?
• Challenges with current microservice adoption
in enterprises.
• Microservice Catalog – An introduction, context
and advantages.
• How Microservice Catalog(s) operate.
• Enterprise-grade options
• Conclusion
Agenda :

5. • Enterprises are under
more pressure to
innovate faster and
increase product velocity.
• It is agreed by the
industry thought leaders
that enterprises that are
not able to effectively
support microservices
will be less able to
compete in the future.
• Enterprises who have
adopted microservices
are more likely to
perform well against
metrics like development
efficiency, the ability to
use new platforms,
collaboration across
teams and sharing of
services across
applications.
Context : Microservices have taken over enterprise IT by
storm
As per O’Reilly Microservice adoption report, 77% of respondents have adopted
microservices.
5

6. Service Explosion : State of Microservice sprawl in well-
known enterprises
Tremendous scale of microservices at Uber , mid-
2018, observed by the distributed tracing tool
Jaeger
State of microservices at Netflix.

7. Enterprise-wide microservice adoption – Challenges ,
Part 1
• Microservices are great as long as they are limited to 5-
10, and not more.
• The chaos that comes with microservices, start appearing
as cracks in the system, and becomes noticeable when
you have 30+ microservices.
• Over time, this becomes unmanageable, and when
something breaks, your operations team have no idea
who to reach, to handle/fix that issue.
• There is no clear ownership, nobody knows who to
contact if a particular service breaks.
• No easy way to search for a service to be able to
reuse/consume it across the enterprise.
• No way to easily access documentation/related
information about a service, and how to consume it.

8. Enterprise-wide microservice adoption – Challenges ,
Part 2

9. Microservices : A threat to scaling an enterprise ?

10. Solution – A Microservice Catalog
• A microservice catalog is a record/list of all the
microservices that an enterprise has in its ecosystem.
• It tracks all the services that an enterprise is running in
production, and describes information about those
services - what each service does, who owns it, and how
to operate it.
• Using a microservice catalog, any user in the enterprise
can quickly find a service, it's usage, it's owners, and so
on.
• It gives an enterprise a sense of governance and control
at scale, as you have a single source of truth that you can
start to refer to, while trying to answer other questions.

11. Functional representation of a Service Catalog :
Service Publishers and Consumers

12. Microservice Catalog : A single source of truth

13. Microservice Catalog : Open source or Enterprise-
grade options
Ortelius is a unified microservice
catalog designed to track and
version your microservice software
supply chain along with all
consuming ‘logical’ applications.
DeployHub simplifies cloud-native
architecture by governing your
microservice supply chain in one
place.

14. Conclusion
• Scaling microservices and the challenges associated with it, particularly when it comes
to needing an enterprise-grade tool to manage it, might appear trivial at first, when you
only have a few services, but once you cross the magic mark of 30-50 services, it
actually starts making sense to invest in a solution to this problem.
• Fortunately, there are quite a few tools, and approaches available in the market, which
focus on how an engineering team can start solving this issue, at scale.
• You can start small, but ensure this is a part of your overall engineering strategy,
and approach, so that you at least have all the information and metadata handy,
when you do decide to go for an enterprise-grade service catalog office.

15. Questions, anyone ?

16. Thank you
More Info:
• Ortelius.io
• https://github.com/ortelius
Follow Ortelius:
• linkedin.com/company/ortelius-open-source
• @OrteliusOs
Follow me:
• https://twitter.com/turjachaudhuri
• https://www.linkedin.com/in/turjac591/