Cart
[Home] [By Thread] [By Date] [Recent Entries]
2/26/2002 3:01:31 PM, "Bullard, Claude L (Len)" <clbullar@i...> wrote: > I've got serious guys here who say tightly coupled > web services are the way to go. I'd be awfully curious to know the reasoning behind that. I thought that "tight coupling" was a famous design anti-pattern, more or less antithetical to "modularity." Web services would seem to be that LAST place one would want to use tight coupling . I can understand why people *want* to extend conventional programming paradigms to the internet. It's not obvious how far that will take us ... certainly to the LAN, probably to the intranet ... but Don Box's article makes it clear that even SOAP-RPC's most fervent advocates acknowledge that it hits the wall when we try to take that to the Web. "Fix HTTP to be RPC-friendly" is a perfectly logical response (although "fix the messaging model to be HTTP-friendly" seems a bit more practical to me). But I can't understand why someone would think that "tightly coupled web services are the way to go" UNTIL the standard internet hardware and software infrastructure make this feasible. Oh, yeah, and faster-than-light communication is invented, assuming we want to coordinate the war against the aliens with tightly coupled web services :~)
|
