How to glue micro instances together?

[Jonarod]

Hello, first of all thank you for this great package, love it!

I have hard time to understand if micro could act as a glue for other micro-services ?

In a REST-like service, I imagine multiple micro-services could be host under the same endpoint like: api.domainName.com/
api.domainName.com/users/
api.domainName.com/todos/
etc... with each endpoints corresponding to one micro-service, thus each responsible for one particular micro-task.

The question is: how should I glue them all?

I have seen alusion to NginX ( #11 ) as load balancer... which implies learning one more tool, relying on another service... before going to that direction I'd prefer using tools I have at my disposal. In a minimalistic and simple approach, I would orient myself using micro by implementing routing like proposed in #16.

The unique constraint I have is indeed, how to serve .js entry points or .html files from micro?

Going one step further with the whole zeit.co mega-cool packages, should micro be the master server/router of other micro services, Next.js webapps, serve projects etc...? How ?

I mean, I would love to create a micro instance able to serve Next.js webapps or a simple html file or an image etc...

What do you guys think about such approach?

[Jonarod]

Ok, I found that I am a baby-newbie in the microservice world...

If you are like me, follow this link: How to route microservices with NginX

I first sight I thought it would be another whole ballpark to configure... but after reading the post, it turns out proxy routing is stupid simple to implement and worked out of the box for me.

Hope this helps someone else.