Answer the question
In order to leave comments, you need to log in
How to organize internal communication of microservices with each other?
If I want to make my service as atomic as possible, consisting of many small services, and not make some of these services public, but leave them for debugging and internal inter-service communication. How to properly organize the internal communication of microservices?
In particular, if the service is made on Node.JS & Express, then how to organize the communication of components with each other so as not to load the HTTP server and how to close some routes for external users?
Answer the question
In order to leave comments, you need to log in
Organize a data bus based on, for example , zeromq (it is often used in the context of microservices). There is even something ready , as an example.
When we switched to microservices, we also faced a similar problem. And they wrote their own library. Works faster than through zeromq. there is no intermediary, only a direct socket connection.
You can get the server part here https://www.npmjs.com/package/aud-socket-server and the client part here https://www.npmjs.com/package/aud-socket-client
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question