What is the default config for SOA? Why don’t we try and solve the 95% before we move on to the edge cases?
Big SOA with reg/rep and so on- who needs it? Who is using it? Remember UDDI? It was designed to handle WSDL complexity. But very few organisations needed it. UDDI was designed to offer extreme configurability. Who most likes extreme configurability? Consultants.
Enterprises need to stop and ask themselves what problems they are actually trying to solve, rather than what problems they ever might need to solve. What does the business actually need, not how do we spend this budget? Developers can handle exceptions – that is what they’re there for. Jeff seems to disagree, although I am not sure.
The Java world is finally getting it, with Spring bringing convention over configuration to JEE’s complex API set.
SAP began to show real value when the vendor and its customers began to understand useful generic configurations. What’s canned SOA? That’s what we need to work out. I don’t think SOA is dead – I just think it needs to grow up… and act a little more conventional.