Then I had to explain him what it means by having an Application qualified to be SOA. I must admit that I learnt about SOA from the discussion happening in this group. Good on you guys.
But in the process what I was forced to ask myself is "Are we not heading towards another Paradigm Shift". We started as a stove-pipe kind of applications and then we switched over to n-tier apps and now we are talking about Application Re-use rather than Function / Class reuse.
Cheers :)
Samir Kumar Mishra
Tel: +61-403-747-809
Email: [EMAIL PROTECTED]
Home: http://samirmishra.tripod.com/
My Attitude in life is best described by my Blood Group… B +ve
On 3/14/06, Anne Thomas Manes <[EMAIL PROTECTED]> wrote:
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
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
