One of the more intersting trends I'm seeing in software is the rapid move towards simpler services like RSS and REST for connecting systems of all kinds together.  It's not that SOAP and WS-* aren't terrific, but they can be much harder to use and often require white-robed experts to apply properly.  George Morimisato, one of the co-authors of the SSE standard has been quoted as saying "the chance of a standard being adopted is inversely proportional to its complexity."  And folks, some of our SOA technologies are just too unwieldy.

I've been talking a lot lately about the bustling world-wide information ecosystem, with the vast networks of blogs, feeds, filters, aggregators, search engines, mash-ups and more as creating a Global SOA (SOA definition here).  I originally explored these ideas seriously a few months ago and received quite a bit of encouraging feedback.  Further discussions have resulted in some invited speaking engagements here in the DC area where I discuss Web 2.0 and it's close connection and overlap with SOA concepts like composite applications, software as a service, information supply chains and more.  It does seem that people are quite eager for easier ways to build SOAs.

And in case you're not sure any of this is important, Gartner has recently claimed that by 2008, 80% of all software development will be based on SOA principles. It, like Web 2.0, is the future.

• Simpler Integration is Faster and Higher Quality: I talked about this in my article 5 Reasons Why Web 2.0 Matters, but Web 2.0 concepts encourage using simpler, easier to use standards, and more malleable integration techniques.  Mash-ups instead of composite applications, RSS/REST instead of SOAP, etc.  My assertion is that these simpler approachs are cheaper to build, easier to maintain, and less prone to breakage.
  
• Stronger Loose Coupling: Traditional SOA technologies force you to control the other end of the conversation.  While sometimes this is absolutely necessary, old school SOA requires it whether you need it or not.  Web 2.0 approaches to integration don't encourage this absolute control and foster a much more lightweight, loose-coupled syndication approach instead of forceful integration.
  
• A Complete Tolerance Continuum: Mainstream behind-the-firewall SOA has an absolute, rigid view of functionality and integration.  Web 2.0 is more free wheeling, though sometimes to a fault admittedly.  So I'm not advocating the replacement of our SOA tools and technologies at all, just the addition of Web 2.0 techniques both for lighter weight integration and for better software including architectures of participation, real-time feedback mechanisms, social immersion, tagging/folksonomies for organizing information instead of taxonomies, data as the new functionality, etc.

posted Tuesday, 13 December 2005 10:45 AM EST