MicroServices separation by folder naming convetions

[ghost]

Hi, Is it possible
to separate the microservices by folder naming convention?
Or by a service.json file, inside a folder, which would describe the (to compile) code scope and limit the execution only to a special service environment.

It could be something like the already implemented balancer solution:
"Every node can be a balancer"
This would be:
"Every Node can be any of the possible services inside one project"

This could also simplifie the code base, because we could share code between services without copy & paste of files between different meteor projects, because we would have only one project. And it would be very easy to start using services for existing projects.

So my question is, is it possible and are there some limitations to solve it?
This would also make possible of a MotherShip solution, because we would know about all the microservices in a project ;)

And a lot of thanks, to Arunoda and all the MeteorHacks Guys which are helping a lot to improve meteor.
Really great work all that stuff!

[ghost]

With a MotherShip solution i mean, a central place for my project where I can see all my services and get some useful data about all the different nodes and microservices which are running, and maybe have a control over starting, stopping etc.

[arunoda]

It's an interesting idea. We haven't though that yet.
Currently, we are working on multi-core support. After that's we'll back to improve microservices.
I'll think about this as well.

[rhyslbw]

+1

[ghost]

I guess the UI for the services overview is already planned as a kadira feature.
Would be really cool ;)