“SOA met its demise on January 1, 2009, when it was wiped out by the catastrophic impact of the economic recession. SOA is survived by its offspring: mashups, BPM, SaaS cloud computing, and all other architectural approaches that depend on ‘services.’”
–Anne Thomas Manes, vice-president and research director at Burton Group
1. If SOA is truly dead, we might as well have poured all that money into the U.S. housing bubble.
2. If SOA is truly dead, we have allowed the recession to limit IT’s contribution to business agility.
3. If SOA is truly dead, we should all get used to a lot less interoperability.
4. If SOA is truly dead, we’ll never see the full benefits of server consolidation and virtualization projects.
5. If SOA is truly dead, don’t count on cloud computing or SaaS to fill the gap.
6. If SOA is truly dead, we’ve taken one step forward and two steps back.
7. If SOA is truly dead, it was never properly defined and understand by business leaders.
8. If SOA is truly dead, it was an experiment worth trying – and worth trying again.
9. If SOA is truly dead, we’ll never see the forest for the trees.
10. If SOA is truly dead, IT deserves to be considered a cost centre.
11. If SOA is truly dead, there’s a great history to be written from all the blog posts.
12. If SOA is truly dead, IBM and many other vendors will lose some serious revenue.
13. If SOA is truly dead, we’re getting caught up in semantics rather than what’s important.
14. If SOA is truly dead, we might as well kill off a lot of other data centre improvements, too.
15. If SOA is truly dead, the IT managers aren’t the only ones who have lost credibility.
16. If SOA is truly dead, there will be a lot fewer conferences to attend.
17. If SOA is truly dead, Gartner, IDC and Forrester should have warned us.
18. If SOA is truly dead, application development will reach a standstill, too.
19. If SOA is truly dead, there ought to be plenty of people at the funeral.
20. If SOA is truly dead, we should all give our heads a shake.