Skip to main content

Hi everyone,

We recently evaluated the LeanIX Self-Built Software Discovery, specifically the Microservice Discovery feature, for both our backend microservices and frontend applications (e.g., Android app).

During this evaluation, we observed that the leanix.yaml file in each repository automatically generates Application factsheets with the subtype Microservice in LeanIX. However, it appears there is no way to configure this to create factsheets of type "IT Component", which we currently use in our metamodel. The only changes that can be made are to the subtype, which can be set to deployment, microservice or business solution.

Our current modeling approach:

We’ve defined in our metamodel that software components, organized hierarchically within a solution, should be represented as IT Components, typically with the subtype Software.

As a result, we’re now facing a redundancy:

  • The Microservice Discovery creates Application/Microservice factsheets automatically.

  • We already manually model the same software components as IT Component/Software factsheets.

 

We would like to continue using Microservice Discovery for both backend and frontend components, but are unsure how to best integrate this with our current modeling strategy.

We’re looking for advice or best practices around the following questions:

  1. How should we handle this situation?

  2. What is the conceptual difference between an Application/Microservice and an IT Component/Software?

  3. Is there a recommended way to structure or relate these factsheets hierarchically?

    For example:

    • We have a Application/Business Solution: “ABC”

    • Under ABC, there is a backend and frontend (“XYZ Backend”, “XYZ Frontend”)

    • Each backend component (for backend “XYZ”, backend “QWE” and so on..) then includes multiple microservices

Any input, experience, or best practices you could share would be highly appreciated!

Thanks in advance!
Fred

You must understand that the LeanIX Self-Built Software Discovery is all about integrating SBOM’s into LeanIX and let LeanIX convert that output into IT Components. That is the main value adding concept here.

With the manifest schema and integration script (used in deploy/build/... pipeline) you then refer to which Business Applications your Microservice are delivering a service. Or even refer to other MS subtype factsheet

Then within the Microservice factsheet or in the manifest file (yaml config file) you can add the “type” of service as property on the fact sheet (default settings): backend, ui-focused/front-end,...

You can create a hierarchical MS / box-into-box structure to group the actual MS’s into your backend XYZ, QWE groups?

Or eliminate that logical grouping, and add it as an extra enumeration property on the MS factsheet, or use a tag for that XYZ, QWE grouping?

 

Reply


Terms & ConditionsCookie settings