So, uh, duh
I was a bit annoyed when people suddenly stopped saying S-O-A and started saying so-ah, or as I like to point out, “So, uh…” That was only a pronunciation change. The worst that could come out of that would be kids in the National Spelling Bee asking, “Are there any alternate pronunciations?” (It was on in our corporate fitness center during my workout today…)
Well, if you haven’t heard, Gartner and Oracle have both starting using the term SOA 2.0. With some liberal pronunciation from a French descent, that now yields, “So, uh… duh!” That about sums it up. Duh! We don’t need “2.0”. Go sign this petition and stop the madness.
2 Responses to “So, uh, duh”
Leave a Reply
[…] Since many people pronounce SOA as "so-uh," Todd Biske recommends adding the French pronunciation of the number two (deux, pronounced "duh") and call it "so-uh duh." (Pardon my French…) […]
[…] Joe McKendrick of ZDNet picked up on my so, uh, duh… blog entry regarding the new SOA 2.0 moniker. My previous post merely pointed to the petition to stop the madness. Something that is unfortunate in all of this is the actual reasoning behind the new moniker. Oracle and Gartner are trying to encourage the incorporation of events into SOA efforts. This, outside of the name, is actually a good thing. Bloggers like Brenda Michelson (eBizQ, elemental links) and Mike Herrick have posted on the importance of event driven architecture and its relation to SOA, as have I. Others out there clearly feel that EDA is a subset of SOA, and therefore there is no need to call it out. Personally, I think there is a risk that the need for events can get lost. A service is something that is available for the public good. It has to be requested. An event does not necessarily represent a request. It is merely a statement of something that has happened. What makes events so great is that anyone who is interested can choose to take action. The source of the event is not required to have any expectations of actions that will take place. It certainly can, but it doesn’t have to, unlike a service request. If we come back to the goals of SOA, a key one is agility. I don’t see how we can be agile without events. They bring exposure to happenings to a wider audience than the silo in which the action happened. That’s what it is all about. If we don’t break down the silos, we can’t be successful. Stop the madness. Ensure your architecture fully embraces services AND events. Just don’t call it SOA 2.0. […]