TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Why You Need a Microservice Catalog

16 pointsby kenroseabout 5 years ago

1 comment

kenroseabout 5 years ago
Hey everyone, I&#x27;m Ken, one of the founders at OpsLevel.<p>My co-founder John and I were early employees at PagerDuty (in fact, John was the first hire at PagerDuty). We noticed that companies running large microservice deployments all ended up building internal tooling to help catalog and track the microservices they had in production (e.g., Spotify has System-Z, Shopify has ServicesDB, LinkedIn has Service Scorecard). We saw this as a greater need, so decided to build OpsLevel, a service catalog for everyone else.<p>In the article above, John talks about the organizational problems that occur when you have lots of microservices and some different ways of addressing them.