Hi Bryan, I'm working on the post, slowly ;-). In the meantime, right now, we have a federated ESB architecture with one ESB in the US and one in the Philippines (probably will be adding a third in Korea eventually). Our current ESB is Software AG's Crossvision Service Orchestrator. Since SAG recently bought WebMethods, the combined company will be combining their ESB/Integration server products into a new offering later this year. We'll eventually upgrade to that product. We are using web services, message queues, JDBC connectors, FTP, email, directory watching, http post, and custom Java adapters for our endpoints. We have canonical data model for most of our transaction types (this is one of the most important things you will need to do), and we're currently transforming and pushing millions of messages through the bus a month. Our ESB is used for both internal integration, and for RosettaNet based B2B integration.
We've been at this for a little over two years now, and are just heading down the governance road where we'll be putting the infrastructure, policies, etc. in place to better manage what we've built. UDDI will be a part of this. Right now, we're not exposing much in the way of services to our application developers, so it's been relatively easy to manage up until now (we've mostly been using the ESB to integrate existing systems). There are several governance products we've looked at, and there is a lot of promise, but there's also a lot of complexity (and cost) to most of them. -Rob On Apr 2, 9:13 am, "Bryan Hogan" <[EMAIL PROTECTED]> wrote: > Rob, > > I am in the process of implementing SOA and ESB. I would love to read > your follow-up blog post. I have broken the point-to-point architecture > that was a plague into a hub-and-spoke architecture. I do not like this > due to the fact that it is a single point of failure. Because of this I > have been slowly moving towards an SOA. Any information you would share > would be a great benefit. It would be great if you could write it in a > ColdFusion context. > > What comprises your ESB? How do you manage, log and provide APIs? > Another point I have been pondering is having my developers use these > services in the base application's architecture. However, I am still > debating on whether to add another layer for them and keep the services > available to customers and internal integration needs outside the normal > application's architecture. > > Thanks, > Bryan > > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf > > Of Rob Brooks-Bilson > Sent: Wednesday, April 02, 2008 12:44 AM > To: CFCDev > Subject: [CFCDEV] Re: architecture question: communication between > applications > > I'd love any additional feedback you might have. I still owe a part-2 > for the post, I just haven't had a chance to write it all up yet. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
