This section will introduce you to the Technology space within VSM, with information around used tech is maintained.
The Technology space is the second of the three big areas of the LeanIX VSM tool. Here all the information about a company's engineering stack is centrally documented.
What is a service?
A service to VSM is every independently deployable object - a microservice, micro frontend, a larger monolith, or some other type of service in a service-oriented architecture. It does not count individual deployments, rather 1 service can be simultaneously deployed multiple times.
At the core of the Technology space sits the service catalog. Same as other VSM catalogs, it can be tagged to further differentiate types of services or allow for another custom filtering.
For each service, a service page with specific details exists. From a basic description and relations to the Team and Product areas of VSM over links to external resources, the centrally relevant information is collected on this front page. In different tabs, we can find information sourced programmatically from different sources, such as code repositories.
The library catalog is a global repository of the libraries and their corresponding licenses used in an organization. Sourced from software bills of material (SBOMs), it is a reliable source of direct and transitive dependencies of the service landscape. Akin to the other catalogs, it can be tagged to customize the collected data, such as recommending a remediation strategy centrally.
The API catalog provides central documentation around all APIs set into the context of the service and product catalogs. Tags can also be utilized here and are typically employed to differentiate high-level technical information of the APIs, such as their different authorization concept or release stages.
For each API exists a page with information on the specific catalog entry. Starting with basic information such as the description, version, and providing and consuming services, it can also be customized with tags for more detail. The dependent products and teams are automatically sourced from the service relation.
Updated about 2 months ago