If I start 3 instances or marmot with embedded nats, they won't cluster automatically, because they do not have the right config and they do not have knowledge of each other ?
So I was thinking of some sort of discovery mechanism, so that each embedded nats modify its config at runtime.
Synadia Cloud can do this for us, with each Marmot Embedded NATS telling Synadia that it booted and subscribing to others that booted. All we need is a common namespace.
If I start 3 instances or marmot with embedded nats, they won't cluster automatically, because they do not have the right config and they do not have knowledge of each other ?
So I was thinking of some sort of discovery mechanism, so that each embedded nats modify its config at runtime.
Synadia Cloud can do this for us, with each Marmot Embedded NATS telling Synadia that it booted and subscribing to others that booted. All we need is a common namespace.
You can see a KV thats generic enough here using NATS: https://github.com/delaneyj/toolbelt/blob/main/nats.go#L87