Cart
[Home] [By Thread] [By Date] [Recent Entries]
It doesn't tell us a lot that we don't already know, but it isn't too far off the mark for what it does say. In other words, not terribly informative but not wrong. Again, I see web services as a good way to get edge systems to communicate with the enterprise applications. I don't see them as a great architecture for fine-grained, high frequency, communications. A model for systems that already work like that pre-web, pre-XML is NCIC. It is global, functional, mature and well-implemented. If one takes that path, the ramp up to web services will go slower than expected and .NET can be seen as a part of the application development environment, not the core of it. But what we see is often based simply on what we need today so my perspectives are limited. len From: Jonathan Robie [mailto:jonathan.robie@d...] I would be curious to hear what people think of the following article, which attempts to describe the current state of web services: Web Services Review Mark Waterhouse. Web Services Architect http://www.webservicesarchitect.com/content/articles/mark04.asp Is this a good overview of where we are at? Does it leave out anything important? Is it balanced?
|
