{"action":"created","issue":{"url":"https://api.github.com/repos/MassTransit/MassTransit/issues/577","repository_url":"https://api.github.com/repos/MassTransit/MassTransit","labels_url":"https://api.github.com/repos/MassTransit/MassTransit/issues/577/labels{/name}","comments_url":"https://api.github.com/repos/MassTransit/MassTransit/issues/577/comments","events_url":"https://api.github.com/repos/MassTransit/MassTransit/issues/577/events","html_url":"https://github.com/MassTransit/MassTransit/issues/577","id":157400123,"number":577,"title":"Reliable messaging","user":{"login":"voroninp","id":9202028,"avatar_url":"https://avatars.githubusercontent.com/u/9202028?v=3","gravatar_id":"","url":"https://api.github.com/users/voroninp","html_url":"https://github.com/voroninp","followers_url":"https://api.github.com/users/voroninp/followers","following_url":"https://api.github.com/users/voroninp/following{/other_user}","gists_url":"https://api.github.com/users/voroninp/gists{/gist_id}","starred_url":"https://api.github.com/users/voroninp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/voroninp/subscriptions","organizations_url":"https://api.github.com/users/voroninp/orgs","repos_url":"https://api.github.com/users/voroninp/repos","events_url":"https://api.github.com/users/voroninp/events{/privacy}","received_events_url":"https://api.github.com/users/voroninp/received_events","type":"User","site_admin":false},"labels":[{"id":268199536,"url":"https://api.github.com/repos/MassTransit/MassTransit/labels/discussion","name":"discussion","color":"fad8c7","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2016-05-29T18:57:29Z","updated_at":"2016-12-10T15:41:41Z","closed_at":null,"body":"As far as I understand `MT` in comparison to `NServiceBus` does not support [reliable  messaging](https://vimeo.com/111998645) out of the box. (correct me, if I'm wrong, I'd be very happy to be mistaken).<br/>\n\nYet I see an option of using the underlying RabbitMQ for that purpose.\nHere is the workflow:\n- do some biz rules\n- generate special correlation id\n- store this id in db\n- publish a message\n- commit transaction\n\nBut instead of going to consumers message first goes to a special 'loopback queue', where it is processed by the sender/publisher part or by some dedicated service which has a task of looking inside DB for a corresponding correlation id, and in case of success putting message in correct exchanges.\n"},"comment":{"url":"https://api.github.com/repos/MassTransit/MassTransit/issues/comments/266216832","html_url":"https://github.com/MassTransit/MassTransit/issues/577#issuecomment-266216832","issue_url":"https://api.github.com/repos/MassTransit/MassTransit/issues/577","id":266216832,"user":{"login":"voroninp","id":9202028,"avatar_url":"https://avatars.githubusercontent.com/u/9202028?v=3","gravatar_id":"","url":"https://api.github.com/users/voroninp","html_url":"https://github.com/voroninp","followers_url":"https://api.github.com/users/voroninp/followers","following_url":"https://api.github.com/users/voroninp/following{/other_user}","gists_url":"https://api.github.com/users/voroninp/gists{/gist_id}","starred_url":"https://api.github.com/users/voroninp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/voroninp/subscriptions","organizations_url":"https://api.github.com/users/voroninp/orgs","repos_url":"https://api.github.com/users/voroninp/repos","events_url":"https://api.github.com/users/voroninp/events{/privacy}","received_events_url":"https://api.github.com/users/voroninp/received_events","type":"User","site_admin":false},"created_at":"2016-12-10T15:41:41Z","updated_at":"2016-12-10T15:41:41Z","body":"@alexeyzimarev  So should we perform publishing before committing a database transaction when consuming another MT message, and publish after commit when processing was not initiated within consumer? Unfortunately, there is nothing in docs concerning MT's in-memory outbox."}}
{"actor":{"display_login":"voroninp"}}