Egon (EGG) Kuster's Home Page - Blog: Enterprise Agility: ESB, SOA, Web Services

October 21, 2004

Enterprise Agility: ESB, SOA, Web Services

Web Services Pipeline has another great article about web services by Fred Cummins. This article talks about enterprise agility and how Enterprise Services Bus (ESB), Service Oriented Architectures (SOA) and Web Services can help create an agile organisation. The article is a must read for anyone interested in the way web services are heading as it identifies a good list of requirements to support an Agile environment, or really any large web services deployment. The article also goes onto to concisely identify the middleware requirements and the components that create a complete enterprise service environment.

Links
Web Services Pipeline Article

Posted by Egon Kuster at October 21, 2004 11:45 PM

Comments

Egg, this article looks like the usual meaningless drivel that companies like EDS are spouting. I mean, he talks about the demise of "hub and spoke" architectures and the SOA "enterprise bus" and then goes on to define a fuzzy description of a hub-and-spoke arch using SOAP. There's no "bus" here at all. He also talks about the need for a publish/subscribe notification bus, but doesn't talk about how that fits with a SOA. He mentions subscribing to "topics", which indicates he's probably just thinking about JMS or another channel-based messaging system - a "traditional" system that he's bagging. And there's no technical detail really here at all. In fact, what does he actually mean by "The typical message transport layer binding will be TCP/IP using HTTP; however, there may be alternatives to HTTP, and a new version of HTTP may require a different binding". Does he really think a new version of HTTP is likely? Am I missing something? Posted by: Matthew Phillips at October 27, 2004 11:05 AM

It is a high level article that is only about the concepts behind SOA rather than the technical details and that is all that it is supposed to be. SOA is nothing new at all, it is the same crap that has been around for years with things like CORBA, COM, DCOM, etc. Web services just provide the lowest common denominator to allow different systems to have a common language to communicate. You are not missing anything, but I do think that you are trying to read too much into this article. The article is only about the concepts, and yes there are many other articles like this already out there. What this article does is provide a good collection of the common concepts and ideas contained in many of the other articles. Posted by: Egon Kuster at October 27, 2004 07:37 PM


	« Power Charging Pad \| Main Blog Page \| Fighting for the TV Remote? » October 21, 2004 Enterprise Agility: ESB, SOA, Web Services Web Services Pipeline has another great article about web services by Fred Cummins. This article talks about enterprise agility and how Enterprise Services Bus (ESB), Service Oriented Architectures (SOA) and Web Services can help create an agile organisation. The article is a must read for anyone interested in the way web services are heading as it identifies a good list of requirements to support an Agile environment, or really any large web services deployment. The article also goes onto to concisely identify the middleware requirements and the components that create a complete enterprise service environment. Links Web Services Pipeline Article Posted by Egon Kuster at October 21, 2004 11:45 PM Comments Egg, this article looks like the usual meaningless drivel that companies like EDS are spouting. I mean, he talks about the demise of "hub and spoke" architectures and the SOA "enterprise bus" and then goes on to define a fuzzy description of a hub-and-spoke arch using SOAP. There's no "bus" here at all. He also talks about the need for a publish/subscribe notification bus, but doesn't talk about how that fits with a SOA. He mentions subscribing to "topics", which indicates he's probably just thinking about JMS or another channel-based messaging system - a "traditional" system that he's bagging. And there's no technical detail really here at all. In fact, what does he actually mean by "The typical message transport layer binding will be TCP/IP using HTTP; however, there may be alternatives to HTTP, and a new version of HTTP may require a different binding". Does he really think a new version of HTTP is likely? Am I missing something? Posted by: Matthew Phillips at October 27, 2004 11:05 AM It is a high level article that is only about the concepts behind SOA rather than the technical details and that is all that it is supposed to be. SOA is nothing new at all, it is the same crap that has been around for years with things like CORBA, COM, DCOM, etc. Web services just provide the lowest common denominator to allow different systems to have a common language to communicate. You are not missing anything, but I do think that you are trying to read too much into this article. The article is only about the concepts, and yes there are many other articles like this already out there. What this article does is provide a good collection of the common concepts and ideas contained in many of the other articles. Posted by: Egon Kuster at October 27, 2004 07:37 PM