Data Model

Flexible data model - no need for any redeployment

While a major benefit of Microservice Intelligence is the ready-made import e.g. from CI/CD or Kubernetes, you can leverage the advantages of the flexible data model. See LeanIX Data Model or Self Configuration for details.

Data model basics

The Microservice Intelligence datamodel.

The Microservice Intelligence datamodel.


Domain is a representation of a logical clustering of managed microservices, helping you keep track of how they support your business.

They can be front end or backend, business-driven domain.


Product is the representation of the business applications and products that are served to the end-user.

Products are connected to and often come from the very applications defined in a LeanIX EA Suite.


Team is the responsible development team behind the Microservice, allowing easy identification of responsibles and experts in your microservice landscape.


Microservice the core Fact Sheet in Microservice Intelligence.

It is a representation of a service itself, not the Deployments that are instances of the service.


API covers the offered and consumed APIs of the microservices.

Understand what is the data flow amongst the API and the Microservice.

Data Object

Data Object is the object that is being transferred from an API, e.g., a survey result from a polling API or an event.


A Deployment specifies how the Microservice is being served to the end-user, e.g., on a certain Kubernetes Cluster.

Subtypes help to group Deployment by technology, e.g. CronJob or Stateful Set for Kubernetes.


Library contains the software libraries used by a certain Deployment.

Using Libraries helps reduce the software footprint and standardize the creation of Microservices.

Technical Component

Technical Components represent any technical dependencies of the Microservice, Deployment, or API.

Examples are Databases, Programming Languages or Images.

Compute Environment

Compute Environment shows the environment in which deployments are run, e.g., a Kubernetes Cluster.

Compute Environments can be of category Application Server or Cluster.


Violations are the concrete instances of Violation Types, including the mitigation state. Take active control of your pressing risks and raise awareness to the entire organization.

Violation Type

Violation Types are the classes of availability, best practice, cloud spend, obsolescence, performance, or security that are raised in a hyperscaler or security tool.

Data model connections

It is possible to connect Microservice Intelligence to other LeanIX workspaces. The best practice connections are showcased below:

  • Microservice Intelligence to Enterprise Architecture Suite:
MI to EAS data model mapping.

MI to EAS data model mapping.

  • Microservice Intelligence to Cloud Intelligence:
MI to CI data model mapping.

MI to CI data model mapping.

Updated 2 days ago

Data Model

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.