I like to find out what would be the next generation of Web Services like? You may talk about the current limitations of the present generation of Web Services and predict how it will be like when the technology matures.
A few areas I could think of will be security and distributed transactions. Perhaps, also on the improvement of performance over the wire, etc. Any thoughts will be much appreciated.
The security and coordination specifications are coming (some are already here, but few implementations are available yet). I could also imagine that a standard, binary version of SOAP etc. will become relevant at some point (or perhaps we'll go back to CORBA eventually...)
The reason why RMI doesn't cut it in this scene is that it's not platform independent. Naturally, JRMP (as the native RMI protocol) is the best protocol if you're in total control of your environment and every system is known to have a JVM to talk to. This is not the case in many places.
I'd watch the SOA areas and WSDL 2.0 Message Exchange Patterns.
Joined: Dec 25, 2003
The following quote is found in the editorial review of Service-Oriented Architecture: A Field Guide to Integrating Xml and Web Services by Thomas Erl,
The emergence of key second-generation Web services standards has positioned service-oriented architecture (SOA) as the foremost platform for contemporary business automation solutions. The integration of SOA principles and technology is empowering organizations to build applications with unprecedented levels of flexibility, agility, and sophistication (while also allowing them to leverage existing legacy environments).
I would like to invite Thomas to comment on what will constitute the 2.5 or 3rd generation Web Services and what impact it will have on the SOA and the industry? What would be the situation for companies who are lacking behind in the adoption of SOA?
Thanks [ June 16, 2004: Message edited by: Frankie Cha ]
Standards considered part of the first-generation Web Services framework are WSDL, SOAP, UDDI. (These, of course, rely on pre-existing standards, such as XML, XML Schema and HTTP.)
There are many second-generation standards that have surfaced, each addressing a specific extension to the first-generation framework. These specifications are often referred to as WS-* standards, because most of them are prefixed with "WS-". The development of most of these standards was driven by major software manufacturers, many of which collaborated. Some standards have been widely accepted, while others failed to gain any support.
There are too many to list here, but some of the key (and more established) WS-* specifications that you should be aware of include: - WS-Coordination (for context management) - WS-AtomicTransaction (for ACID transaction support) - WS-BusinessActivity (for long-running transactions w/o rollback) - BPEL4WS (for orchestration workflow logic) - WS-Security (a framework of standards governing Web services security) - WS-ReliableMessaging (for message acknowledgement and delivery failure reporting)
If you would like to learn more about any of these specifications, have a look at http://www.ws-standards.com/ and check out http://www.specifications.ws/ for links to the actual specifications. The ws-standards site also contains a diagram that illustrates how these standards inter-relate.