I'm currently in the middle of something with insane deadlines, many vendors and constant changes to those vendors services. Yet, the Neudesic Services team I'm working with is keeping up with those changes as they come in even though they have to accomodate all of those changes as soon as they occur.
Why? because every change made is just naturally handled by Neuron's typeless endpoints, pub sub capabilities and a code step that alters the Topic based on SOAP Action.
If we had burdened the teams changing things every day with an intermediary that assumed strongly typed schemas as their main paradigm then they would have failed already.
Not only that, when they asked if we could prevent a message from being sent to a target service based on a condition when they had a security concern we answered. "Yes. We can add that and do it in seconds. We can also do it live without a recompile or a deployment"..
None of this reaction time would be possible if we had forced people to work against a WSDL the bus published. That would have forced them to use us to develop with or go through an extra step of telling us what version they wanted exposed yada yada...
When things settle down and they actually want to lock down endpoints based on a schema we can add a validation pipeline. But until then I'm glad we actually start out with a chance to keep up!
You need to be a member of Neuron ESB User Network to add comments!
Join Neuron ESB User Network