{"action":"created","issue":{"url":"https://api.github.com/repos/SocketCluster/socketcluster/issues/383","repository_url":"https://api.github.com/repos/SocketCluster/socketcluster","labels_url":"https://api.github.com/repos/SocketCluster/socketcluster/issues/383/labels{/name}","comments_url":"https://api.github.com/repos/SocketCluster/socketcluster/issues/383/comments","events_url":"https://api.github.com/repos/SocketCluster/socketcluster/issues/383/events","html_url":"https://github.com/SocketCluster/socketcluster/issues/383","id":304138144,"number":383,"title":"Workers spread horizontally but one main process?","user":{"login":"Tuccinator","id":6589165,"avatar_url":"https://avatars2.githubusercontent.com/u/6589165?v=4","gravatar_id":"","url":"https://api.github.com/users/Tuccinator","html_url":"https://github.com/Tuccinator","followers_url":"https://api.github.com/users/Tuccinator/followers","following_url":"https://api.github.com/users/Tuccinator/following{/other_user}","gists_url":"https://api.github.com/users/Tuccinator/gists{/gist_id}","starred_url":"https://api.github.com/users/Tuccinator/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Tuccinator/subscriptions","organizations_url":"https://api.github.com/users/Tuccinator/orgs","repos_url":"https://api.github.com/users/Tuccinator/repos","events_url":"https://api.github.com/users/Tuccinator/events{/privacy}","received_events_url":"https://api.github.com/users/Tuccinator/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-03-11T07:51:00Z","updated_at":"2018-03-14T03:03:48Z","closed_at":null,"author_association":"NONE","body":"I've been testing around with Socket Cluster and I'm enjoying it a lot. The one use-case I have for it would be to have workers spread out over multiple servers but all connected to a main master. So essentially the master will run some operations and publish to a Redis server. Each of the workers will be subscribed to this Redis channel and receive the data through that. Is there a specific way I should implement this or what?"},"comment":{"url":"https://api.github.com/repos/SocketCluster/socketcluster/issues/comments/372889432","html_url":"https://github.com/SocketCluster/socketcluster/issues/383#issuecomment-372889432","issue_url":"https://api.github.com/repos/SocketCluster/socketcluster/issues/383","id":372889432,"user":{"login":"Tuccinator","id":6589165,"avatar_url":"https://avatars2.githubusercontent.com/u/6589165?v=4","gravatar_id":"","url":"https://api.github.com/users/Tuccinator","html_url":"https://github.com/Tuccinator","followers_url":"https://api.github.com/users/Tuccinator/followers","following_url":"https://api.github.com/users/Tuccinator/following{/other_user}","gists_url":"https://api.github.com/users/Tuccinator/gists{/gist_id}","starred_url":"https://api.github.com/users/Tuccinator/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Tuccinator/subscriptions","organizations_url":"https://api.github.com/users/Tuccinator/orgs","repos_url":"https://api.github.com/users/Tuccinator/repos","events_url":"https://api.github.com/users/Tuccinator/events{/privacy}","received_events_url":"https://api.github.com/users/Tuccinator/received_events","type":"User","site_admin":false},"created_at":"2018-03-14T03:03:48Z","updated_at":"2018-03-14T03:03:48Z","author_association":"NONE","body":"The main process must only be run on one instance so in my case it wouldn't need to scale horizontally, but it's workers which connect to it will need to. Essentially there is a primary process on it's own server that all the workers will publish their data to. Do you think it would be fine to separate the entire logic of the primary process away from the socket cluster, into its own process, and only access the said primary process through Redis?"}}
{"actor":{"display_login":"Tuccinator"}}