endpoint.tv - WCF Partner Neuron ESB
- Posted: Jan 30, 2010 at 1:36 PM
- 52,358 Views
- 5 Comments
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
Right click “Save as…”
Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation,
please create a new thread in our Forums,
or
Contact Us and let us know.
Follow the Discussion
Oops, something didn't work.
What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.sign up for email notifications?
I looked into using Neuron for a project I working on about a year ago and would have loved to use it, but our product is a shrink wrapped and needed to scale from small to large installs, but there wasn't really any flexability in the neuron pricing, would love to know if this has changed.
Not a problem, we offer OEM licensing to many customers. Not sure who you spoke with at the time, but feel free to contact us at NeuronInfo@neudesic.com and we can discuss pricing further. If you reference this endpoint.tv show, I'll know what's up. Thanks,
NServiceBus could be a good alternative for you - reference 3 DLLs and you're done.
http://www.NServiceBus.com
We're actually using that, or actually SimpleServiceBus as back then NServiceBus had far to many DLL's. We've look at NServiceBus, MassTransit, WSO2 and several others.
Our biggest issue is that we need central auditing support, which tends to a more hub & spoke design than nsb seems to offer. We also have geo-located nodes and hub to hub trunking is also an important feature. Haven't looked at 2.0 yet, are last eval was done against 1.9.
1.9 actually had too few DLL's and resulted in all sorts of versioning conflicts when used together with other OSS libraries. It was 1.8 that had the overly-high DLL granularity. It's our hope that 2.0 finds just the right balanace.
You don't need to give up all the benefits of the fully distributed deployments that NServiceBus supports to achieve "central auditing support". You have the ability to direct all audit messages to a central location with 1.9 as well as 2.0 by setting the ForwardReceivedMessagesTo attribute of UnicastBusConfig.
Hope that addresses your issues.
Remove this comment
Remove this thread
close