-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using multiple Orleans clusters (multiple clients) #211
Comments
Currently, a client is limited to an app domain. So it is possible to connect to more than one cluster by initializing clients for different clusters in different app domains, although this is an obvious hassle. Yes, we'd like to remove this limitation. Ideas and PRs are welcome. |
To add to what Sergey wrote, it is quite easy to host each client in a separate app domain. You can follow the example here of how to start a silo in a separate app domain. It would be quite similar for the client. |
OK, I see. A bit of a hassle indeed but probably workable for now. Thanks! |
This is being tracked by #467. |
As far as I can tell, currently there is no way of an application to use more than a single client to communicate with Orleans.
But, what about a scenario of having multiple Orleans clusters, each providing different services (and grains)?
If you want to build multiple backend systems running on Orleans, without coupling them into a single cluster, there's no way of communicating with them from a single application (as you can't instantiate multiple clients).
This means you have to add an additional layer on top of that (providing, for instance, a REST interface in front of each cluster), which is a big overhead if there's no need to expose these to the outside.
Is there an intention to make the client to be an instance and not static so you can create multiple clients to multiple clusters?
The text was updated successfully, but these errors were encountered: