Hacker News new | ask | show | jobs
by iainmerrick 68 days ago
No, I think you’re not reading it literally enough. “Microservices” generally does mean separate HTTP (or at least RPC) servers. Near the beginning, the article says:

A microservice has a very well-defined surface area. Everything that flows into the service (requests) and out (responses, webhooks)

1 comments

I think a better word would have been "modularization" than "microservices" as I also highly correlate "microservices" with http-based calls.
Really? That seems strange, at least to me.

While HTTP can be considered as a transport layer for RPCs between microservices, it seems to me to be a very inefficient and bug-prone solution.

Can you describe a set up where you used HTTP between microservices?

> Really? That seems strange, at least to me.

Are you purposely misreading the comment? Where did it say that http was the only form of communication (or even the best) between microservices? Where did it imply there weren't other methods?

> While HTTP can be considered as a transport layer for RPCs between microservices, it seems to me to be a very inefficient and bug-prone solution.

This is so irrelevant to the point being made it's nuts.