{"action":"opened","issue":{"url":"https://api.github.com/repos/harlow/go-micro-services/issues/16","repository_url":"https://api.github.com/repos/harlow/go-micro-services","labels_url":"https://api.github.com/repos/harlow/go-micro-services/issues/16/labels{/name}","comments_url":"https://api.github.com/repos/harlow/go-micro-services/issues/16/comments","events_url":"https://api.github.com/repos/harlow/go-micro-services/issues/16/events","html_url":"https://github.com/harlow/go-micro-services/issues/16","id":191487764,"number":16,"title":"NATS or NSQ","user":{"login":"joeblew99","id":11999859,"avatar_url":"https://avatars.githubusercontent.com/u/11999859?v=3","gravatar_id":"","url":"https://api.github.com/users/joeblew99","html_url":"https://github.com/joeblew99","followers_url":"https://api.github.com/users/joeblew99/followers","following_url":"https://api.github.com/users/joeblew99/following{/other_user}","gists_url":"https://api.github.com/users/joeblew99/gists{/gist_id}","starred_url":"https://api.github.com/users/joeblew99/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joeblew99/subscriptions","organizations_url":"https://api.github.com/users/joeblew99/orgs","repos_url":"https://api.github.com/users/joeblew99/repos","events_url":"https://api.github.com/users/joeblew99/events{/privacy}","received_events_url":"https://api.github.com/users/joeblew99/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-11-24T10:45:06Z","updated_at":"2016-11-24T10:45:06Z","closed_at":null,"body":"thanks for this example - really easy to follow along.\r\n\r\nI am wanting to put a Message queue within this architecture and wanted ro tun it by you and well the whole internet :)\r\nI am still trying to work out the best way, without introducing too much boiler plate into it.\r\n\r\nBasically, the API code where the REST / JSON layer is exposed would put JSON messages onto a Message queue topic.\r\nThen the GRPC Service would listen for them.\r\n\r\nWhy do this ?\r\nBecause then a GRPC Service can also call other GRPC services as and when they need to.\r\nThis allows building larger systems of Microservices where the Choreography is emergent.\r\n\r\n\r\n\r\n\r\n\r\n\r\n"}}
{"actor":{"display_login":"joeblew99"}}