halturin
commented
1 year ago https://github.com/ergo-services/examples/blob/master/cloud/producer/go.mod Is correct ?
Yeah, this is correct, but it has an artifact :). The last line must be removed for sure (forgot to do that).
Is this because the type is on the consumers side and you want the producer to send the consumer well known types ?
producer imports consumer to be known of the consumer's message type. You definitely can move it out from the consumer package to somewhere else. But the main idea is to keep message types close to the owner (cmd/consumer in this case). Anyway, it's just an example.
Also this begs the question , do producers and consumers know about each other at compile time ?
Ergo implements Erlang technologies, including EPMD. In Ergo this feature is embedded into the node, so you don't have to worry about that. It's like a local registrar of the running nodes keeping the node name and port number. Before making a TCP-connection, say to "abc@localhost", your node automatically resolves the port number requesting EMPD for the information where node "abc@localhsot" serves incoming connections.
- In this example, for regular network connection, the producer connects to the consumer resolving the port number using EPMD.
- for the cloud connection - once the node is connected to the cloud, it becomes a cluster member with a single virtual "namespace". All connections to the *@"namespace" are routed through the cloud connection (basically, it uses a proxy feature for that).
gedw99
https://github.com/ergo-services/examples/blob/master/cloud/producer/go.mod Is correct ?
Is this because the type is on the consumers side and you want the producer to send the consumer well known types ?
Also this begs the question , do producers and consumers know about each other at compile time ?