Business in general and IT in particular are often obsessed with finding "best practices." I suppose the logic is, if you know what constitutes a best practice, you can duplicate it and create your own success.
But the reality is, mistakes can often teach us just as much, if not more, than those best practices-assuming we take the time to actually learn from them. Just ask any successful entrepreneur.
So, in the spirit of learning from our mistakes, I've found a little weekend reading for you: "Four SOA Implementation Worst Practices: Why Service-Oriented Architectures Fail and How to Prevent It."
This article, published on Information Management, is by Jake Freivald, the vice president of marketing at business intelligence and Web reporting software provider Information Builders. Now, I know what you're thinking. This is going to be another list that tells you SOA's failure is because you forgot governance or something like that. While that is a commonly cited reason for SOA failure, I think you'll find Freivald's list offers a fresh look at SOA mistakes. Here it is:
- Overemphasizing low-level code.
- Centralizing design and development.
- Ripping and replacing legacy software.
- And buying software without support.
See what I mean?
Freivald is specifically tackling worst practices related to using SOA as an integration solution. Now, I know, some people say SOA shouldn't be used for integration. The whole point is to avoid that point-to-point, tight coupling stuff. But if it's done right, SOA can solve a lot of your integration problems. So, let's move on ....
This is also a great article for those who are struggling to define services, because many of these problems boil down to how you deploy services. For instance, low-level code is all about making services too small in impact. So the article spends a good deal of space discussing what a service should be, what it shouldn't be, what happens when services are too granular and so on.
He also tackles another common misstep: Mistaking SOA for enterprise application integration, v. 2.0.
Another interesting item in this insightful article is Freivald's observation that these four mistakes are typically "the result of wanting to ride the latest technology wave without balancing the hype with practical knowledge and experience." And really, isn't that the basis of all too many IT mistakes?
After you've finished reading about the worst SOA practices, balance your reading by checking out these posts on what it takes to ensure SOA success:
- Seven Strategies for SOA Success Learned in 2008
- Lessons Learned in Two Years of SOA
- The Coast Guard's Best Practices for SOA
Have a good weekend.