This seems like such a basic topic that I’m almost afraid to ask it, but it is a source of confusion for our user base and the LeanIX docs are kind of silent on the subject, so here goes: how would you describe to a LeanIX newbie the difference between a service IT component and a software IT component?
Question
For IT components, how do you differentiate a service from software?
+1
HI
My usual guidance on the topic is that Software is usually something centrally hosted and that you most of the time have to install, while services are usually a “on-demand” type of case that you access, like a SaaS, or something custom developed like a micro-service.
If you notice, once you link an Application to our SaaS Catalog, it creates an IT Component of the Service type.
Does that help? Any examples in specific that you have in mind?
Hi
We define Service to be an internally built and deployed microservice, which aligns somewhat with the guidance from
+1Our lens so far has been what is discoverable by other tools (like ServiceNow) versus what is not. This seems to align with what
I may be adding to the confusion here, but there it goes nothing 😁
My mental model is: business capabilities ← technology services ← applications ← technology components
So business capabilities are enable / automated by technology services which are provided by applications that are made by technology components.
But there is another angle on technology components: things you install and own, which typically have SKUs and are discoverable, and things provided by external entities you buy / subscribe to (e.g. security bulletins), which typically are not discoverable.
Thing is, “service” is such an overloaded term 😱
Login to the community
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.