Keith Pleas Blog

Keith's palimpsest

What is SOA?

I've been spending the week at a "peer" retreat on Enterprise Architecture in Crested Butte (Colorado). The small event (there are 16 people this year) is organized by Martin Fowler and Bruce Eckel and has been running for several years now.

The participants have historically been J2EE oriented, but more recently there have been some .NET-centric participants. This is the first real opportunity I've had to sit down and talk at length with people from the "other" camp, and it's been tremendously useful for me. Not only that, but guys from Sun and IBM picked up my lunch tab at Brick Oven Pizza yesterday. <grin>

The "sessions" are basically BOFs (birds-of-a-feather) lead by one of the participants, and might include anywhere from 3 to as many as a dozen of us. One interesting breakout the first day was on the topic "What is SOA" and was lead by Bobby Woolf, who co-authored the recent book Enterprise Integration Patterns with another retreat participant Gregor Hohpe. The highlight of that session was Sean Neville breaking everyone up with the line "It's SOAP without the P" (which sounds much funnier when spoken aloud). There were a number of stabs at a real definition of SOA - including one "it's basically an API" that pretty much nobody agreed with. And others by people from a couple of the major players in this area who said "Web Services" which, again, everyone else said was too narrowly focused. One thing that everyone seemed to agree on, though, was that SOA included workflow - and probably BPEL. Hmm...maybe those BizTalk guys are onto something after all. <grin>

Comments

Jimmy Nilsson said:

Ah, I'm glad to hear that you had a good time Keith. Well, I can't say I was worried.
:-)

Best Regards,
Jimmy
www.jnsk.se/weblog/
###
# August 19, 2004 2:01 PM

TrackBack said:

# August 20, 2004 12:07 AM

TrackBack said:

# August 20, 2004 4:22 PM

TrackBack said:

# September 23, 2004 1:42 PM

Lyronne Rangan said:

At the end of the day, it is about business. It's about keeping our jobs. It's about the smoke and mirrors. It's sadistic. Let's face it. If we were really interested in making life simpler by design, we would have one operating system, one programming language, one architecture, one design, one cost. We are not making life simpler. We are responding to the push and pull of the industry which has become so far removed from business, so agnostic of domains we have terms like BPM,EAI,SOA,BPEL etc etc that companies believe they need to have it because they dont and they just keep plugging legacy code onto it. What are we distributing for? Because we have always done it? because deploying execs to clients is an intensive maintenance excersice? We would not have a legacy if we really thought about the impact of change and the cost of maintenance, we would be refactoring toward deeper insight of our domains and bringing domain logic logistically closer and closer stripping out the stifling, configuration heavy infrastructure.

# May 21, 2008 12:19 PM
Leave a Comment

(required) 

(required) 

(optional)

(required)