Lets think there are two mesg services called as Service A and Service B that created with their own mesg.yml files.
Service A may want to communicate with Service B over the private shared Docker network. But since there is no an option of setting human readable service names with the yml file or with the service starting api by using a –name flag, it’s required to use this kind of log names like
core-f6c5f0abefc66ddb6a80565238fa69e8340582af-service which is hard to use and not static. We need static names otherwise it’s required to update Service B when source code of Service A is changed.
I propose to having the ability of setting static names to services inside yml file or/and with the –name flag on service starting/creation.
We also need to create a special network where all services are connected to each other but not their dependencies. Otherwise we can have conflicts in names because each dependencies has their own static names.