RabbitMQ handling recieved topic events
Say I'm consuming a channel with a queue that's bound to mulitple routing keys.
So for example I'm recieving events such as user.updated, order.created etc.
When I recieve these events, what is a correct way to handle them?
In the example in the documentation (which uses pubsub) a subscriptionmanager is used. This subscription manager contains the events (as string) and their handlers. So when you get an event, you look for the corresponding handler and fire the handle method. I guess for topics a similar approach could be used?
Is this the way handling events is done in enterprise applications? What other methods are there? One problem I can see occuring is that when the serialized event from App A, gets deserialized at app B but doesn't match anymore because a field or whatever got added.
To prevent this a common "event" library could be created that holds all the events, but I have read in multiple articles it's bad practise to share libraries among MicroServices.
GITHUB:
RabbitMq pub/sub:
https://github.com/dotnet-architecture/eShopOnContainers/blob/master/src/BuildingBlocks/EventBus/EventBusRabbitMQ/EventBusRabbitMQ.cs
RabbitMq subscription manager:
https://github.com/dotnet-architecture/eShopOnContainers/blob/master/src/BuildingBlocks/EventBus/EventBus/InMemoryEventBusSubscriptionsManager.cs
The docs:
https://docs.microsoft.com/en-us/dotnet/standard/microservices-architecture/multi-container-microservice-net-applications/rabbitmq-event-bus-development-test-environment
c# events rabbitmq
asked Nov 27 '18 at 15:34
BartKrulBartKrul
769
add a comment |
Say I'm consuming a channel with a queue that's bound to mulitple routing keys.
So for example I'm recieving events such as user.updated, order.created etc.
When I recieve these events, what is a correct way to handle them?
In the example in the documentation (which uses pubsub) a subscriptionmanager is used. This subscription manager contains the events (as string) and their handlers. So when you get an event, you look for the corresponding handler and fire the handle method. I guess for topics a similar approach could be used?
Is this the way handling events is done in enterprise applications? What other methods are there? One problem I can see occuring is that when the serialized event from App A, gets deserialized at app B but doesn't match anymore because a field or whatever got added.
To prevent this a common "event" library could be created that holds all the events, but I have read in multiple articles it's bad practise to share libraries among MicroServices.
GITHUB:
RabbitMq pub/sub:
https://github.com/dotnet-architecture/eShopOnContainers/blob/master/src/BuildingBlocks/EventBus/EventBusRabbitMQ/EventBusRabbitMQ.cs
RabbitMq subscription manager:
https://github.com/dotnet-architecture/eShopOnContainers/blob/master/src/BuildingBlocks/EventBus/EventBus/InMemoryEventBusSubscriptionsManager.cs
The docs:
https://docs.microsoft.com/en-us/dotnet/standard/microservices-architecture/multi-container-microservice-net-applications/rabbitmq-event-bus-development-test-environment
c# events rabbitmq
asked Nov 27 '18 at 15:34
BartKrulBartKrul
769
add a comment |
Say I'm consuming a channel with a queue that's bound to mulitple routing keys.
So for example I'm recieving events such as user.updated, order.created etc.
When I recieve these events, what is a correct way to handle them?
In the example in the documentation (which uses pubsub) a subscriptionmanager is used. This subscription manager contains the events (as string) and their handlers. So when you get an event, you look for the corresponding handler and fire the handle method. I guess for topics a similar approach could be used?
Is this the way handling events is done in enterprise applications? What other methods are there? One problem I can see occuring is that when the serialized event from App A, gets deserialized at app B but doesn't match anymore because a field or whatever got added.
To prevent this a common "event" library could be created that holds all the events, but I have read in multiple articles it's bad practise to share libraries among MicroServices.
GITHUB:
RabbitMq pub/sub:
https://github.com/dotnet-architecture/eShopOnContainers/blob/master/src/BuildingBlocks/EventBus/EventBusRabbitMQ/EventBusRabbitMQ.cs
RabbitMq subscription manager:
https://github.com/dotnet-architecture/eShopOnContainers/blob/master/src/BuildingBlocks/EventBus/EventBus/InMemoryEventBusSubscriptionsManager.cs
The docs:
https://docs.microsoft.com/en-us/dotnet/standard/microservices-architecture/multi-container-microservice-net-applications/rabbitmq-event-bus-development-test-environment
c# events rabbitmq
asked Nov 27 '18 at 15:34
BartKrulBartKrul
769
Say I'm consuming a channel with a queue that's bound to mulitple routing keys.
So for example I'm recieving events such as user.updated, order.created etc.
When I recieve these events, what is a correct way to handle them?
In the example in the documentation (which uses pubsub) a subscriptionmanager is used. This subscription manager contains the events (as string) and their handlers. So when you get an event, you look for the corresponding handler and fire the handle method. I guess for topics a similar approach could be used?
Is this the way handling events is done in enterprise applications? What other methods are there? One problem I can see occuring is that when the serialized event from App A, gets deserialized at app B but doesn't match anymore because a field or whatever got added.
To prevent this a common "event" library could be created that holds all the events, but I have read in multiple articles it's bad practise to share libraries among MicroServices.
GITHUB:
RabbitMq pub/sub:
https://github.com/dotnet-architecture/eShopOnContainers/blob/master/src/BuildingBlocks/EventBus/EventBusRabbitMQ/EventBusRabbitMQ.cs
RabbitMq subscription manager:
https://github.com/dotnet-architecture/eShopOnContainers/blob/master/src/BuildingBlocks/EventBus/EventBus/InMemoryEventBusSubscriptionsManager.cs
The docs:
https://docs.microsoft.com/en-us/dotnet/standard/microservices-architecture/multi-container-microservice-net-applications/rabbitmq-event-bus-development-test-environment
c# events rabbitmq
c# events rabbitmq
asked Nov 27 '18 at 15:34
BartKrulBartKrul
769
asked Nov 27 '18 at 15:34
BartKrulBartKrul
769
asked Nov 27 '18 at 15:34
BartKrulBartKrul
769
asked Nov 27 '18 at 15:34
BartKrulBartKrul
769
asked Nov 27 '18 at 15:34
BartKrulBartKrul
769
769
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53503039%2frabbitmq-handling-recieved-topic-events%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53503039%2frabbitmq-handling-recieved-topic-events%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
