Facts:
A service can rely on other services
types of relation :
parent child : a service create another one. (usually a high level service that wraps other services
utilization : a service use an action from another services
In the case of a parent child relation. It is required for the parent services to keep track of how to reach the robots of all the services it has created. Currently this needs to be done manually by the template creator using the shame of the parent service.
The idea would be to provide an interface in the service template API that provide a way to keep track of the relations.
Benefits:
unified way for developer to model services relations
allow to have some background routines making sure that all children are properly deleted in case some robots were offline during deletion of the parent service
automatic state update and self-healing : parent watch child states and trigger self-healing actions automatically to keep the application running.
Facts: A service can rely on other services types of relation :
In the case of a parent child relation. It is required for the parent services to keep track of how to reach the robots of all the services it has created. Currently this needs to be done manually by the template creator using the shame of the parent service.
The idea would be to provide an interface in the service template API that provide a way to keep track of the relations. Benefits:
API: Info required to reach a service :