Skip to content
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

RFC: expose erlang pg's scope ability for Phoenix.PubSub.PG2 #183

Closed
xiaoqinglee opened this issue Apr 7, 2024 · 1 comment
Closed

RFC: expose erlang pg's scope ability for Phoenix.PubSub.PG2 #183

xiaoqinglee opened this issue Apr 7, 2024 · 1 comment

Comments

@xiaoqinglee
Copy link

Process groups can be organised into multiple scopes. Scopes are completely independent of each other. A process may join any number of groups in any number of scopes. Scopes are designed to decouple single mesh into a set of overlay networks, reducing amount of traffic required to propagate group membership information. Default scope pg is started automatically when kernel(6) is configured to do so.

start_link/1

pg was contributed by Maxim Fedorov from WhatsApp. Maxim’s work is focused on performance and scalability of the server side.

pg

WhatsApp deprecated and removed wandist. With pg it is possible to create any number of disjoint sub-clusters (by running several pg scopes).

@xiaoqinglee xiaoqinglee changed the title RFC: expose erlang pg's scope feature for Phoenix.PubSub.PG2 RFC: expose erlang pg's scope ability for Phoenix.PubSub.PG2 Apr 7, 2024
@josevalim
Copy link
Member

We don't plan to expose this in our default implementation but you can provide your own adapters to PubSub that relies on scope. Thank you!

@josevalim josevalim closed this as not planned Won't fix, can't repro, duplicate, stale Apr 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants