{"action":"created","issue":{"url":"https://api.github.com/repos/nestjs/nest/issues/758","repository_url":"https://api.github.com/repos/nestjs/nest","labels_url":"https://api.github.com/repos/nestjs/nest/issues/758/labels{/name}","comments_url":"https://api.github.com/repos/nestjs/nest/issues/758/comments","events_url":"https://api.github.com/repos/nestjs/nest/issues/758/events","html_url":"https://github.com/nestjs/nest/issues/758","id":328772565,"node_id":"MDU6SXNzdWUzMjg3NzI1NjU=","number":758,"title":"microservices module in cluster/load balancing environment","user":{"login":"roeehershko","id":12342000,"node_id":"MDQ6VXNlcjEyMzQyMDAw","avatar_url":"https://avatars0.githubusercontent.com/u/12342000?v=4","gravatar_id":"","url":"https://api.github.com/users/roeehershko","html_url":"https://github.com/roeehershko","followers_url":"https://api.github.com/users/roeehershko/followers","following_url":"https://api.github.com/users/roeehershko/following{/other_user}","gists_url":"https://api.github.com/users/roeehershko/gists{/gist_id}","starred_url":"https://api.github.com/users/roeehershko/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/roeehershko/subscriptions","organizations_url":"https://api.github.com/users/roeehershko/orgs","repos_url":"https://api.github.com/users/roeehershko/repos","events_url":"https://api.github.com/users/roeehershko/events{/privacy}","received_events_url":"https://api.github.com/users/roeehershko/received_events","type":"User","site_admin":false},"labels":[{"id":604589895,"node_id":"MDU6TGFiZWw2MDQ1ODk4OTU=","url":"https://api.github.com/repos/nestjs/nest/labels/type:%20discussion%20%F0%9F%94%A5","name":"type: discussion 🔥","color":"fbca04","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-06-02T19:56:56Z","updated_at":"2018-10-04T15:03:27Z","closed_at":null,"author_association":"NONE","body":"## I'm submitting a...\r\n<!-- \r\nPlease search GitHub for a similar issue or PR before submitting.\r\nCheck one of the following options with \"x\" -->\r\n<pre><code>\r\n[ ] Regression <!--(a behavior that used to work and stopped working in a new release)-->\r\n[ ] Bug report\r\n[*] Feature request\r\n[ ] Documentation issue or request\r\n[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.\r\n</code></pre>\r\n\r\n## Current behavior\r\n<!-- Describe how the issue manifests. -->\r\nThis is more of a discussion, currently the microservices module works good as long as you have 1 process, but once you add load balancing or clustering (which is a must in microservices applications)\r\nit become harder to work with since messages will but fired to all the services even if they are the same services under a loadbalancer, the protocol doesnt know that.\r\n some of the messaging protocols have a way around it such as MQTT \"group\" mode but not sure that redis/nats has one.\r\ni can just create mqtt transport that support the groups mode, but you think its better to provide  support for this in nest? \r\nit is microservice transport protocol and load balancing is a big part of it"},"comment":{"url":"https://api.github.com/repos/nestjs/nest/issues/comments/427053566","html_url":"https://github.com/nestjs/nest/issues/758#issuecomment-427053566","issue_url":"https://api.github.com/repos/nestjs/nest/issues/758","id":427053566,"node_id":"MDEyOklzc3VlQ29tbWVudDQyNzA1MzU2Ng==","user":{"login":"rychkog","id":1942440,"node_id":"MDQ6VXNlcjE5NDI0NDA=","avatar_url":"https://avatars1.githubusercontent.com/u/1942440?v=4","gravatar_id":"","url":"https://api.github.com/users/rychkog","html_url":"https://github.com/rychkog","followers_url":"https://api.github.com/users/rychkog/followers","following_url":"https://api.github.com/users/rychkog/following{/other_user}","gists_url":"https://api.github.com/users/rychkog/gists{/gist_id}","starred_url":"https://api.github.com/users/rychkog/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rychkog/subscriptions","organizations_url":"https://api.github.com/users/rychkog/orgs","repos_url":"https://api.github.com/users/rychkog/repos","events_url":"https://api.github.com/users/rychkog/events{/privacy}","received_events_url":"https://api.github.com/users/rychkog/received_events","type":"User","site_admin":false},"created_at":"2018-10-04T15:03:27Z","updated_at":"2018-10-04T15:03:27Z","author_association":"NONE","body":"> I was able to get load balancing working using NATS queuing.\r\n> \r\n> https://nats.io/documentation/concepts/nats-queueing/\r\n\r\n@triedal How have you managed to pass queue name to the Nest's nats transport?\r\n\r\nAccording to the docs:\r\n\r\n> To create a queue subscription, subscribers register a queue name. All subscribers with the same \r\n> queue name form the queue group. As messages on the registered subject are published, one \r\n> member of the group is chosen randomly to receive the message. Although queue groups have \r\n> multiple subscribers, each message is consumed by only one.\r\n"}}
{"actor":{"display_login":"rychkog"}}