The ECM - SOA divide

Added By Alan Pelz-Sharpe at 26-Jun-2007 | Twitter: @eiwatch |

In the content management world I sense something of a brewing backlash against SOA (Service Oriented Architecture), but I wonder how real or or even practical this is. With most Fortune 2000 firms are already way down the path with SOA, there seems to be no turning back. At the enterprise architecture level, there is no Plan B.

So the issue for me is not whether SOA is the way for ECM, but rather how seriously some of the ECM vendors are embracing it. Almost every vendor has an SOA story, but for most it is less about exposing and consuming services within a heterogeneous architecture -- and more about simply sharing services within their own product line. Also, most vendors have conflated Web Services with SOA, at at time when many thoughtful commentators (c.f., Tim Bray, ZapThink) are questioning the whole Web Services approach. Popping a WSDL on top of a Java API may facilitate integration with .NET applications, but also makes your system more complex, slower, and no more (de)composable than before.

Yet when you promise an SOA approach and charge six and seven figures up for this, delivering short will not make you many friends. SOA represents an opportunity and a challenge to ECM vendors: an opportunity to truly play at the enterprise level, but a challenge in recognizing that ECM represents only a handful of components in a much, much broader mix.

Categories: Alan Pelz-Sharpe, Enterprise Content Management, Industry Standards