Also, Bloomberg said, database management systems are key components of the SOA infrastructure, so it's important to use a DBMS that supports XML natively. Most DBMSs support XML reasonably well, he said, but it's a good idea for organizations to do product comparison to determine if they have the right skills in-house to make the most of the specific XML features found in each product.
Finally, people interested in SOA need to remember that SOA is not a product, it's an architectural approach.
"Do not expect to buy SOA from any [one] vendor," Bloomberg said. "[SOA is] an approach that leverages heterogeneity, so if any vendor says, 'buy my stuff a you'll get a SOA in a box,' they're pulling the wool over your eyes. No vendor can say that truthfully."
Some organizations, like the government offices of Jefferson County, Alabama, simply don't have the time or resources to begin an SOA development project.
According to David Shockey, a systems analyst with Jefferson County, his group is too busy trying to replace legacy mainframe applications with less expensive off the shelf software, all while working within the confines of a tight budget.
"SOA is really not taken into account into our decision making process," Shockey said. "Someday [we'll implement SOA], just not now. There are too many other priorities."
Oracle, SAP and IBM race for SOA dominance
And then there's Big Blue.
"IBM has the broadest and deepest SOA story of any vendor, with their solid software and professional services offerings as well as the depth of each across product lines and verticals," Bloomberg said. "They're everyone's number one competitor."