Bill and I came across this article recently, SOA Not So DOA, which was an excellent, short article. The author had some very good points such as,
“SOA is not a redefinition of modularization, object orientation, componentization. Yes, SOA builds on all three notions but it extends these constructs and thereby creates additional business and IT value. SOA is about integrating the business world with the information technology world in a way that makes both more effective and flexible using services.”
However, the article seemed to abruptly end, just as it was getting to the real meat.
In our SOA: What’s in it for me? series, we discuss how SOA can be perceived and valued by different roles: business, developer, data, and infrastructure. Which extends several of the author’s points. But if you want an elevator pitch for SOA, certainly start with something along these lines from the article:
“Business pressures are compounding as IT constraints are growing. SOA provides an approach to resolve this conflict, which stems from inefficiencies in IT environments and applications turning brittle within five years after deployment. SOA is not a panacea, true, but it is an architectural (business and IT) approach that has a huge upside business impact.”
Now that Bill and I have established some core conceptual notions around SOA we are working on providing a sample SOA implementation. This will span several posts, but we are currently working on an outline to give you an idea of the topics we will cover. Stay tuned!
Print This Post