Closed openainext closed 6 years ago
What do you mean?
I think he meant that if a microservice is strictly a "consumer" (as in they only do broker.call
) instead of providing services.
Would be useful, for example, for transparent migration from monolit app to microservices.
But does it worth? If I understand correctly, you can just create ServiceBroker
instance with no services attached to it and use it as client (after calling .start()
method on it to ensure transporter is connected).
@quex46 it adds overhead. For example, other nodes can care less if the client dies. However, with current architecture, heartbeats and etc will still be sent from the client, which adds overhead.
The client can be separated from the service side