Service Discovery & Catalog

We believe that development speed and ingenuity can be best achieved by empowering autonomous teams. But in fast-scaling development organizations and service landscapes, increasing complexity can quickly become a burden. Therefore, managing DevOps complexity is critical to driving development efficiency and software reliability. The LeanIX microservice catalog is the first step to better understand and navigate the service landscape, responsibilities, and dependencies.

Surfacing microservices and team responsibilities

To create an inventory of your services and the corresponding responsibilities, you start setting up a connection to your GitHub organization and read out all self-developed services based on your repositories' names and descriptions. If you use team entities in GitHub you can understand the responsibilities through the assigned teams or you can ask your developers to create GitHub topics with the team name, such as team-<team-name>.

Our out-of-the-box repository integration will do all the heavy lifting, all you need to provide is an API token. Learn more about our GitHub Repository Integration.

📘

Not using GitHub? Try our CI/CD integrations.

Discover your services and responsibilities with our out-of-the-box CI/CD integrations.

Based on the Microservice Fact Sheet and the related Team Fact Sheet you can already understand who is owning which services. If you define a Domain-Model or Products in your organization you can map both Domain and Product Fact Sheets to your Microservice Fact Sheet to understand: Which Product/Domain is supported by what services and who owns those?

Visualize service, domain, and team relationships in Matrix ReportsVisualize service, domain, and team relationships in Matrix Reports

Visualize service, domain, and team relationships in Matrix Reports

Based on automation, views like this service maintain accurate overviews and provide developers with a central knowledge base to look up service-related information and navigate your service landscape.

Provide table views to look up service dataProvide table views to look up service data

Provide table views to look up service data

Enriching services with deployments & dependencies

Going into more depth of your service landscape, you can now provide additional information on how those services are being developed and deployed. This information is stored on the Deployment Fact Sheet to understand how a particular service is built and deployed at a specific point in time.

Both the Deployment and Library Fact Sheet are populated automatically through our CI/CD integration. You can leverage one of our native plugins for Jenkins, GitHub Actions or Azure Pipelines or hook any other pipeline up to our CI/CD API.

📘

Need more data? Customize our CI/CD integration

The CI/CD integration can also reinforce or even replace the aforementioned repository integration (e.g. with GitHub). Through a yaml manifest we allow you to add a variety of additional information about your microservices and team responsibilities.

Microservice Intelligence shows you the current live deployment while also allowing you to go back and see historical deployments. With this mechanism, you can understand what software libraries were introduced to a certain service at a certain point in time and what dependencies are currently deployed in production.

Navigate along dependencies with the Relations ExplorerNavigate along dependencies with the Relations Explorer

Navigate along dependencies with the Relations Explorer

Understanding service infrastructure & architecture drift

To make the picture on our microservice catalog complete we also want to visualize how our services are running on production infrastructure. Complex pipeline setups with multiple developments and test stages can become overwhelming and it is easy to lose track of what build of your service is actually currently running in production and how they are configured.

Through our Kubernetes integration, we provide you a simple mechanism to understand what version of your service is running on which cluster. We deploy a simple agent to your cluster that scans your K8s objects and sends the information directly to MI.

📘

No K8s? No problem!

With our existing customers, we have also worked on visualizing more traditional infrastructure setups. We are happy to support you!

The Compute Environment Fact Sheet displays your Clusters with their configuration and links them to the Fact Sheets of the microservices that they run. Additionally we add detailed information about your K8s configurations.

Understand what clusters currently run your microserviceUnderstand what clusters currently run your microservice

Understand what clusters currently run your microservice

Additionally we create a Deployment Fact Sheet for any K8s deployment that we track on your cluster. By holding this against the Deployment Fact Sheet from your CICD build & deployment we can detect any infrastructure drift that might occur.


Did this page help you?