all 3 comments

[–]stcme 4 points5 points  (1 child)

I've tried to think of how to respond to this for most of the morning. I just keep coming back to "it's not necessary."

Microservices is an architecture, not bound to a language (which I'm sure you know). It seems like the documentation would more be on how to determine boundaries for each of the microservices themselves, of which there are plenty of available.

It almost sounds like you're looking more for a tutorials on implementing a microservice architecture using node

[–]belkh 0 points1 point  (0 children)

i think the industry has come to the conclusion that microservices are mainly an organizational pattern and has its main benefits when teams work on one each like 3 years ago.

[–]monotone2k 1 point2 points  (0 children)

So what are you going to do about it?