Feature request: dynamic adding of the service to Mesh

Hello,

In my project, I need to have a service mesh (and graphql-mesh actually serves this purpose extremely well), and it would be also nice to have something like a plugin structure. For example, we can have 2 different system installation - first client can have ServiceA and ServiceB installed while the second client can have ServiceA and ServiceC installed. My idea is following - those services register in Mesh (or provide some kind of heartbeat via Redis for example), and I can use the same frontend and Mesh, and just detect those services that were installed/enabled.

It also seems like I can alter the serve task to use some database instead of YAML file but first I want to hear from you, what do you think about that idea.

Start by examining the serve task and how services are currently described in the YAML configuration. Compare that flow with the proposed Redis heartbeat or registration approach, and define the supported configuration and service-discovery behavior before implementation; done means enabled services can be detected for each installation without changing the frontend.

Written by the indexing model from the issue text.