SOA 1.0 is too buggy, let's upgrade to 2.0

With vendors talking SOA into the ground, one is left to wonder what the post-SOA bandwagon will be. Well, it looks like they've latched on to something.

We still may be getting our heads around SOA, but some industry folks appear ready to move on to SOA 2.0. InfoWorld's Paul Krill reported from JavaOne that representatives of both Gartner and Oracle are both invoking the "SOA 2.0" name.

But, but... we're still getting to know SOA 1.0. Most people still haven't even adopted SOA 1.0, for that matter.

The difference between SOA 1.0 and 2.0 is that 1.0 is based on client/server thinking, while 2.0 is based more on event-driven architecture. Gartner's Yefim Natis, for one, is quoted as describing today's SOA as dealing with "a client/server relationship between software modules," with services being subroutines serving clients -- not suitable for every business. SOA 2.0 is an event-driven architecture in which software modules are related to business components, with alerts and event notifications. Examples of SOA 2.0 applications would include order processing systems, hospital admissions processes or bank transactions.

In other words, SOA 2.0 will be faster, sleeker, smarter, and able to handle much larger workloads. And it sounds so compatible with Web 2.0. Great news for marketers, but what about the people in the trenches still trying to solve integration problems and untangle their Spaghetti-Oriented Architectures? Will they even notice, or care, that we're on SOA 2.0 now?