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.

Interview: Steve Jones on "Business-driven SOA"

Posted by Stefan Tilkov on Sep 26, 2007

Sections
Architecture & Design,
Enterprise Architecture
Topics
Business ,
Enterprise Architecture ,
SOA
Tags
Business/IT Alignment ,
Best Practices ,
Business Architecture ,
Adoption
In a new InfoQ interview, recorded at QCon London, Steve Jones head of SOA for Global Outsourcing at Cap Gemini, explains the ideas behind his concept of a "business service architecture", first outlined in his book  "Enterprise SOA Adoption Strategies".

Steve's perspective is interesting because he sees SOA as a concept that is mostly a change of mind, a different view of IT and its organization, rather than a technology issue. His views, while often somewhat provocative, clearly stem from a lot of experience gained in customer projects. Some choice quotes:
Historically IT has been more not as much driving the business but leading it into a pit of despair.
On IT as an architectural profession:
IT really is a paleontology profession, rather than an architectural profession. When we are in support, which is what we do a lot in outsourcing, you can see what the company was doing in 1985, you can see what it was doing in 1990, you can see what is was doing in 1995, and it's just layer upon layer upon layer of systems on top of them.
On "shadow IT":
I think a big change is the rise of situation applications, participation applications, the web 2.0 pieces. The fact that the business is more and more taking these previous Excel generation of applications and wanting to run them on the existing IT estate, this currently called "shadow IT" which is a significant proportion of IT, is business aligned; it's based clearly on the business objectives, it's done by the business themselves or by surrogate IT inside the business. [...]Traditional IT has two choices: it can either move purely into a support role, and a commodity development role, or it can recognize the challenge and really start to move into what is now shadow IT.
Other topics covered include how to apply SOA to existing systems, the problems one runs into when SOA is driven by technology, the structural and organizational impact of business-driven SOA, and motivating both providing and consuming services. Steve also makes the case for adopting the OASIS SOA Reference Model, which he help standardizing.

Watch the interview (18 minutes).
  • This article is part of a featured topic series on SOA

No comments

Watch Thread Reply

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.