InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

The East/West SOA Divide

Posted by Mark Little on Feb 07, 2007

Sections
Architecture & Design,
Enterprise Architecture
Topics
Business ,
SOA

In the past, American adoption of technologies such as CORBA, DCE and J(2)EE has typically out stripped Europe, Japan and other "first world" countries. However, a recent report indicates that for SOA adoption this may not be the case. As the authors point out, most of the oft-quoted SOA success stories are in Europe, Canada, Asia and Australia, with companies in these geographical areas apparently more ready to embrace SOA than their American counterparts. But what are the reasons for this? Is it, as the authors posit, that large vendors dominate the US market and create so much noise about SOA as to confuse "local" users? Or is it that EAI was so dominant in the US compared to elsewhere that it is difficult for SOA based solutions to break the strangle-hold? The only thing that appears to be globally accepted, according to the report, is that SOA has reached acceptance much faster than previous technologies.

The report discusses a number of possible reasons for European dominance of the take-up of SOA. These include that enterprise architecture as a practice is more widely respected and practiced in Europe than it is in the US. As the report says:

Some believe that the IT community in the US is perceived as developer-centric, coding cowboys that care not a whit about architecture. (“Architects? We don’t need no stinkin’ architects.”) While this is a generalization that most likely isn’t true, most large European-based IT shops see enterprise architecture as a way to guarantee that projects don’t go off into the weeds with developers doing their thing without a central coordinating philosophy and organization.

There's also the fact that, due to acquisitions and consolidation activities, many large US firms now have European centric development organizations which lead the SOA effort. Of course there are SOA developments occurring in the US, even for companies with European HQs. It's just that the results indicate that the US isn't ahead as much as would perhaps be expected. This may be a natural effect of the globalization of IT that has been steadily happening over the past few years. As companies are finding with off-shoring efforts in call-centers, banking etc, country borders are quickly becoming irrelevant: work goes where the people and costs dictate. Prior to the general acceptance of the Internet as a critical part of a vendor's infrastructure, globalization didn't exist:

The result was technology adoption that followed the modes of vendor density, marketing dollars, and direct sales outreach: North America followed by Europe and then Japan, Australia, the remainder of Asia, and then Middle East and Africa.

It would appear that the European culture and organizations have a greater desire to adopt SOA than the US. Europe may also have more to gain from the benefits SOA offers, such as loose-coupling and Service reuse.

  • This article is part of a featured topic series on SOA
SOA Adoption in Europe by Tiberiu Fustos Posted
Terminology-nazi response by David Karnowski Posted
  1. Back to top

    SOA Adoption in Europe

    by Tiberiu Fustos

    I agree with the conclusions of the research in the sense that indeed the "showcase" studies are mainly European companies.
    This however is a big difference to effective adoption. A recent initiative by the german IT specialist magazine "Computerwoche" showed that only 7% of the companies with over 100 employees had on-going SOA initiatives. There is an entire analysis on the topic in an article with the significant title "SOA - A paper tiger for German users community" (only in German: www.computerwoche.de/soa-trends/587026/).

    What is interesting beyond the incredible push of the vendors is the significant difference in opinions between the quoted experts. It ranges all the way from "SOA is all about processes" (coming of course from a major BPM vendor to "SOA is only an IT issue" (funnily a quote from one of the showcase SOA companies). The article also mentions that while SOA promises cost savings it starts by a massive investment in new software (ESB etc.).

    Maybe that unlike CORBA, DCOM, EAI etc. - SOA is mainly an umbrella under which many common-sense, established cocepts and competing products find a good and warm place (very much like eBusiness was in the '90s :-) ).

  2. Back to top

    Terminology-nazi response

    by David Karnowski

    In terms of topic your article is very interesting, but the terminology-nazi within me can't let some of the language you used slide:

    1) Your "East/West Divide" title seems to imply that Canada, Europe, and Australia are not considered part of the "West" which, according to your article, only comprises of the US. While "East/West" is probably a poor term to use at all (it was more about industrialized status and political ideology than location), it has historically included all of Western Europe, Canada, and you can throw in Australia as well.
    2) "First world" is not the politically correct term anymore since the collapse of the Soviet Union. "Developed world" and "Developing world" are the more current terms, but even they are breaking down as China, India, and Eastern Europe are straddling a gray area between them.

    Anal-retentively signing off,
    David

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.