Anne,
Of course we don’t lump
you in with those other “analysts” that led the whole ESB = SOA
initiative (we all know who they are). But tell us, how do you think these
individuals came to equate the fact that they need and ESB to create an SOA in
the first place?
JP
From:
[email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of Anne Thomas Manes
Sent: Tuesday, March 14, 2006 7:45
AM
To:
[email protected]
Subject: Re:
[service-orientated-architecture] Re: SOA Infrastructure
You have no idea how many
times in the last year one of my clients has said to me, "I need an ESB.
How do I pick one?"
My response is always, "Why do you think you need an ESB?"
Their response is, "We want to build an SOA."
I take a deep breath and dive into my explanation of SOA:
- SOA is something you do, not something you build.
- An ESB won't give you "instant SOA".
- You don't need a new middleware backbone to do SOA.
- Let's take a look at your issues and requirements...
<sigh>
Anne
On 3/14/06, Dan
Creswell <[EMAIL PROTECTED] >
wrote:
JP Morgenthal wrote:
> Eric,
>
[snip]
> I do believe that SOA is being
undermined by its association with
> the words that are following it and I believe it is being led by the
vendor
> community that is selling tools to this market. Perhaps even
led by the
> analyst community consulting to the vendors helping them to try to
> differentiate themselves in a rapidly commoditized market.
>
Agree but there's a flip side to this.
(Potential) Customers, and in particular their developers, are allowing
this to happen because they don't question and challenge assumptions.
The market has become inverted where rather than the customer saying
"this is what I need now sell me something that fits" they say
"just
give me whatever the current hot tech is".
The vendors and analysts are not experts on their customers' systems -
the customers are and yet the customer refuses to take control of
technology/process/architecture definition and selection.
Imagine you go to your car dealer and you walk in the door. Immediately
they tell you what car you will buy and how much it will cost - they
tell you which model, what colour, what engine size etc Would you
swallow that? Of course not, but we regularly do in the IT world.
I fear that a good chunk of this is due to our commoditization of
programmers. We've thrown out the concepts of expert and aptitude
with
the attendant reduction in quality and the vendors and analysts are
taking advantage (and lets face it, they'd be stupid not to).
Best wishes,
Dan.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
SPONSORED LINKS
YAHOO! GROUPS LINKS
