Node.js micro-services best practices

[soundstep]

Hi Thomas,

Not an issue, I was looking for some up-to-date info, I hope that's ok to contact you from here.
Interesting video there: https://www.youtube.com/watch?v=I1lLzPb3MLg, which was published a year and half ago.

Is this example still up-to-date in a kubernetes scenario?

I know this is a big subject, but I'm looking for solutions for node.js services discovery (like consul), error handling (not sure with what), messaging (rabbitMQ?).

Is there any tool(s) today (end of 2018) that you would recommend? Or do I need to build custom solutions because there no widely-spread tool that I should use?

Thanks in advance if you have a few minutes to direct me.

Cheers.

[tlhunter]

Sorry, I never saw this message of yours!

Kubernetes does make a bit of this obsolete. For example, if your service A depends on service B, kubernetes will expose redundant service B pods using the same DNS name, and will route requests automatically, without service A needing to keep an in-memory list of service B locations.

FWIW, I'm currently writing a book with O'Reilly called Distributed Node.js, which will cover a lot of these technologies. Keep an eye out, it should be published in about a year ;)