I’m looking into the ESB thing with .net like NServiceBus etc , can someone highlight what kind of real world business problems can be solved (forget the technical edge) ? And is this used to integrate different systems.?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m looking into the ESB thing with .net like NServiceBus etc , can someone highlight what kind of real world business problems can be solved (forget the technical edge) ? And is this used to integrate different systems.?
A very popular reason to use it would be to make use of the publisher subscriber pattern.
An example, one command message is sent to an application layer to process some business logic. Once complete a message is published with any updated data to which several services are listening, say a cluster of caches.
There are benefits of side by side versioning. Newer commands could have different names. It can also help if you are interested in using Command Query Separation.
Another would be implementing cross cutting concerns that listen to specific messages.
All in all it’s a very deep subject. However, I would ask what problems you have first? As everything it brings along it own challenges and does certainly not come for free (effort wise I mean not cost).