Business
Nine great unsolved mysteries of SOA
Why is everyone so gaga over cloud computing, yet disinterested in SOA -- even though they're essentially the same thing? This and eight other mysteries are pondered.
In recent years, there has been no shortage of assumptions made about service oriented architecture, many of which have become the conventional wisdom. I posted a few of these raging assumptions over at ebizQ/TechTarget on "nine great unsolved mysteries of SOA." Here is a synopsis:
- What's the difference between SOA and cloud computing? It's about standardized service delivery.
- Why is everyone so gaga over cloud computing, yet disinterested in SOA -- even though they're essentially the same thing? 'Nuff said.
- How could SOA be failing when nobody really has SOA yet? SOA is an evolutionary process, not overnight.
- If SOA is failing so miserably, where are the horror stories? Anyone heard any screams yet?
- How does one know when a SOA project has been successful or unsuccessful? Does anyone really know?
- How many full-functioning, true "SOA" implementations are there, exactly? Some analysts say 10%, some say 90% of companies have it.
- If SOA is "not about technology," why are technologists the only ones driving it? You never hear about the sales department commissioning service oriented architectures.
- How do vendors sell a concept that will make it easier for customers to drop their products? "Hot swappability" means just that.
- Who's paying for SOA? Someone has to pony up to get things started.