I haven't come across a case, but, I would treat micro service as a piece of your overall software solution and can be managed as an instance of BMC_SoftwareServer.
Microservice is software, granted it can seem more complex because it is just a process that can auto-scale and distribute across the network...but Software is Software! I have combined microservices into application models and then technical services because it typically takes many micro services to make an application work and if one piece is down sometimes the relationship is hard to see when the interface is 4-6 layers deep.
So do you use BMC_APPLICATION class template to track microservice ?
What kind of attributes do you manage for a microservice?
Microservices are usually much larger in volume/number to manage - So, how do you reconcile and keep the information current? Do you have any kind of auto discovery integrated for managing microservices?
When you say technical services, are you referring to the infrastructure aspect of the software?
What are the kind of relationships you have for a microservice? I am thinking microservice:microservice (1:1), microservice:application (1:many), microservice: infrastructure (1:1), application:microservice (1:many) -- if these are right, the relationships will be complex and too many to maintain. So, how do you verify the accuracy of relationships?
I am in the very initial stage trying to plan a strategy to manage microservice. So, I have too many questions. All help/info is appreciated.
Thanks & Regards,
I have the same questions;
Is there any update?
Thanks & Best Regards,
2 of 2 people found this helpful
I'm currently building a middleware for this purpose.It extracts data from an APM (application performance management solution) which delivers a real-time view of microservices and it's dependencies and push this information into the CMDB.
Due to the nature of microservices it's hard to keep the CMDB up to date without linking it to any real time information source and synchronize it every now and then (depending on the amount of microservices for a given application we are doing this hourly)