Legacy integrators consolidate; putting policy in charge; trust then validate. A short set of notes this week because there are various deadlines to get out of the way before the Christmas holidays.
# Legacy integrators consolidate. Clientsoft was one of the first mainframe integration vendors to make a strong web services play and it has forged alliances with a number of leading web services specialists over the years. We wrote about some of its customers eighteen months ago in the feature article, More legacy gain than pain with SOA. Now NEON Systems has acquired Clientsoft, adding Clientsoft's web services pedigree to its own established standing in the legacy integration market. I keep on hearing a lot about web services integration of mainframe resources, so this could well qualify as one of those mergers that signals a market moving into the 'acceleration' phase of rapid expansion. But there are a lot of vendors jockeying for position, so I would imagine there will be more mergers and acquisitions before we're through.
# Putting policy in charge is the title of a cogently argued piece by Phil Becker in this week's Digital ID World email newsletter. Phil always does a great job of setting out complex issues in clear terms, and this piece is well worth reading because it explains very clearly all the powerful reasons why "ready or not we must start to turn computing over to automated policy, and putting policy in charge requires identity."
# "Trust then validate" is the Reagan-esque formula put forward by Vordel's Mark O'Neill in this week's opinion piece on why Trust comes first in XML security. I asked Mark to submit this piece after an email exchange in which he picked up on some points made in an earlier feature article we ran in October, Extending the scope of SOA management. Some of the strategies being advanced by vendors in that piece were just plain wrong, he felt, and I thought his arguments were worthy of a wider audience than my inbox. I suspect Phil Becker would agree with Mark's analysis that you'll save a lot of time and effort if you first establish who (or what) a message comes from before you embark on investigating what it contains.