Multiple server versions about hemera HOT 4 CLOSED

@vitorcamachoo hemera is a RPC toolkit which based on the messaging platform NATS. You have to create multiple instances of your service and multiple NATS Server to increase fault tolerance.

NATS can dealing with weak members in your network Pruning.

from hemera.

Hi,
please specify what do you mean with "multiple servers on a NAT". Do you talking about NATS Server or Hemera Client?

but I will try to answer your question.

@vitorcamachoo NATS is a simple pub/sub system. How we communicate with it is standarzied in the protocol. Hemera also have a protocol. As long as we dont change the way how we communicate everything is still backwards compatible.

Scenario 1:
If you talking about a different scenario like

Hemera Instance A with your API version 1.0.0
Hemera Instance B with your API version 2.0.0

here you can easily subscribe to a topic like math:version:1.0.0

act({topic: 'math:version:1.0.0', cmd: 'add', a: 1, b: 2 })

Scenario 2:
Single Hemera Instance with your API version 1.0.0 and 2.0.0.

here you can easily subscribe to a topic like math and change your pattern based on your API version

act({ api: '1.0.0', topic: 'math', cmd: 'add', a: 1, b: 2 })

from hemera.

Hi,
I was talking about multiple Hemera instances spread by version.
The correct scenario is the first one, and that is what I was thinking.

Imagine an Hemera instance depends on [email protected] and make a request:
act({topic: 'math:version:1.0.9', cmd: 'add', a: 1, b: 2 })

If that instance is down, I will received a timeout, and the recovery process to a compatible Math instance (ex: 1.0.1) is through that timeout handling, getting all instances which begin with math:* and filter by the last compatible version and make that request. I'm right?

Thanks.

from hemera.

Thanks a lot for the explanations!

from hemera.