Confused about the myriad definitions of SOA? The first thing you need to know is that it's an architecture. But don't forget that there's more to architecture than a blueprint.

Is your internal software too specialized and therefore too difficult to use with cloud computing, even if you want the cost savings? SOA can come to the rescue.

So you think you don't have the money to find out if SOA can save you money? Test the waters with Open Source SOA. You might find out that Open Source is what you've needed all along.

You don't have to make your SOA services impenetrable. You simply have to make them harder to crack than everyone else's. Use port knocking as an added level of security and crackers won't even know you're there.

Before you can see what's wrong with SOA someone needs to define what SOA is. There's too much confusion surrounding SOA, and that is the beginning of what's wrong with SOA.

SOA is not something you buy, it is something you do. Research shows us that very few companies are doing it well. But the reasons for so many failures are usually people issues, not technology issues. By acknowledging the top 10 reasons people cause SOA to fail, you can put a game plan together that addresses each issue and greatly improves your chances of success.

Fundamental shifts in technology will make it possible for businesses to realize IT’s promise of technology-enabled innovation, responsiveness and speed.