ZeroMQ capabilities -

I am looking for solutions to the scenario.

Let's assume a service-oriented architecture (SOA) with hundreds of services. Services are completely different from what their API is behind an implementation description.

Can different services have different security policies? That is, who can access the service, for example, a service can be completely public, accessible to a subset of employees, may be accessible to the subset of other services. Some services can also be specified at the API level, for example a public service with some internal API calls (Is this a bad habit?).

I have touched a little bit on Zimcu but it is not enough to know if this interconnection can be completed with the ZMQ. Any help to decide whether concentration on ZHMQ is to be continued or not will be highly appreciated.

Are you asking how to handle security in SOA? Or are you asking if it is possible to make a SOA with 0 MQ?

In the past, you need to make it yourself. You need to define your security policy between the services actually does not have 0 MQ domains.

For the next, yes, 0 MQ should allow you to create SOA architecture. In fact we are just fine. Services are explained in the containers with HTTX endpoint controlled by NGNX, which then reverse the requests of one (one or more) nodes server via express, which then reaches the bridge sockets of workers on a fair line basis. Push message. Upon processing the request, the worker sent Push back to the bridge socket of the server. This way we can spin or we want any number of employees with minimal disruption on the server. And this is a service.

The service for service communication is controlled through REST-over-HTTP.