We are into diversified banking and financial services and we deal with CRM, BI, legacy systems, products (in J2EE and .NET) and other heterogeneous platforms. If we want to move to a common platform, why should we choose SOA?
It's best not to think of SOA as a "common platform" -- after all, don't you have enough platforms already? Instead, think of SOA as enterprise architecture that provides an abstraction layer on top of all of your existing platforms and applications that enables you to expose software functionality as agile, reusable services.
We can talk about agility and reusability as business motivations for SOA, but here's a simpler exercise: Ask yourself how your organization has made decisions about integration in the past. Have they chosen the best solution for simplifying integration in the long run, even if that approach costs more and takes more time today, or is the choice to take the cheapest, most expedient approach to integration at the time? Most companies go for the latter. Now ask yourself: What does your architecture look like now -- carefully planned out or spaghetti? If you're like many organizations, taking the cheap, expedient approach to integration leads to spaghetti over the long term. That's one critical motivation for moving to SOA -- dealing with all that spaghetti integration.
Dig Deeper on Topics Archive
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.