Avoid SOA Pitfalls
IT projects have generally a high risk of failure if not managed and executed properly. The risk is even higher, if the project is to define a replacement for the current IT architecture, to overcome agility, scalability, security, extensibility, management or performance impediments. The Service Oriented Architecture is hyped to deliver that, what CORBA and EJB failed to provide, to be the new blanket for hiding the architectural chaos underneath.
When a new technology (or better a methodology) like SOA is not only difficult to master on it’s own, but also hyped (means, proposed by people, who have never written a line of code in their life), it is not a surprise, that “there are instances, where projects are going well, but most are over budget and under delivering, ” says David Linthicum from Real World SOA. He even proposes a money-back guarantee to share the risk, if the consultants take the training on the job on the client’s dime. As this is clearly a little over-provocative, he has a point that it is easy to fail in your job to implement a SOA sucessfully.
Rik de Groot, Viktor Grgic, Vincent Partington, and Gero Vermaas from Xebia posted the top 10 SOA Pitfalls for you to avoid the most common mistakes. They categorized these into implementation, architectural, and most importand also organizational pitfalls. These are the most dangerous, since with SOA also has to come a shift in the organizational culture, which reacts ponderous, sluggish and unwieldy to any attempt to change it. Thanks for the excellent and insightful postings.
With the knowledge about these Top 10 SOA pitfalls, maybe you can give your clients a money-back guarantee!
Tags: SOA