Call for considerations on rpc and event flow restrictions

[robertbetts]

Question 1: Should a nuropb service mesh connection be able to make a request to itself when instantiated as a service ?
Question 2: Should a nuropb service mesh connection be able to subscribe to event topics, that it publishes ?

This is not a debate on conceptually how should these scenarios be handled, and the opinion of the team is that answering yes in both cases is bad practice.

The consideration is whether or not to implement restrictions aimed at preventing these two scenarios, either within the code base or by introducing topic naming and exchange binding conventions that prevent circular flows. Alternatively, should the current more "open" approach continue, leaving the decision to the implementation in deciding on the approach and patterns to follow?