Hi Rob -- Right answer. I think you're right - just keep a healthy phobia of "vendor-driven architecture", and you'll be fine.
But heck, if you already did the architecture first, and you know what you want, and that includes an ESB, then so be it! And we already wrote that what happens when the ESB decision(s) have already been made -- are you screwed? Of course not. Check out our ZapFlash on that subject -- it's been posted here. ZapThink is neutral on ESBs. Use 'em if they work for you (after you defined your architecture). Don't use 'em if they don't work for you (don't feel compelled that you *need* an ESB just 'cause you're doing SOA). And if you already have a few of them in place, deal with it as part of the existing legacy, but don't let that replace the task of actually doing architecture. Have fun! (Beware Ron). Ron --- In [email protected], "Rob Eamon" <[EMAIL PROTECTED]> wrote: > > Odd that you're warning the group about your own company. Burton > Group is a vendor, no? ;-) > > You and Linthicum seem to have an over-developed sense of toolset > vendor phobia. Which seems particularly odd for him since he's spent > most of his career peddling software. > > Is there more to this concern than the reasonable "don't let a vendor > drive your architecture?" > > -Rob > > --- In [email protected], "Anne Thomas > Manes" <atmanes@> wrote: > > > > Beware of vendors! They will lead you astray. > > > > Anne > > > > On Wed, Jul 23, 2008 at 4:42 AM, Michael Poulin <m3poulin@> > wrote: > > > - Michael > > > > > > > > >
