While talking with the application folks about the gaps in my understanding of SOA, one of the architects sent me a document called WebServicesProposal that he co-authored in 2003 after attending the Web Services Edge 2003 Conference. I was amazed how their observations from 2003 are so relevant today and thought it would be great to share this document with you. The authors are Joe Frate and Sean Nally and their document defined Web Services, identified what it can do for our company, documented where it would make sense within our company, and concluded that we should start working on Web Services with a quote of “Web Services is a breakthrough technology that should be taken advantage of.”
They went on to discuss ……
In a nutshell, Web Services is a services-oriented architecture that allows disparate and independent software systems to be integrated using standard message-based protocols for exchanging data. These protocols leverage XML to standardize data representation.
With Web Services, software systems can provide services to each other no matter what platform they are implemented on or what technology they utilize. For example, a software system implemented in J2EE on Unix could access services (and have its own services accessed) by another software system implemented in a COM environment on Windows. Such integration is possible not only for modern software systems, but also for any legacy software system that is enhanced to communicate with a Web Service. This is accomplished by “serializing” the data into a standard XML format, which is then exchanged between two Web Services; this is referred to as “messaging”. When a software system is accessible through a Web Service, we can say that the software system is “wrapped by a Web Service”.
After reading their document, I can see where they have influenced applications development within our company over the last few years by wrapping web services around some of our older application or by replacing client server front ends with java based front ends while leaving the back end database resources unchanged.
Back in 2003, Web Services implied static html pages with a front end web form talking to a backend database or data repository. The Web and Web Services have evolved since 2003 into more than just static pages, embracing a more open social approach to communication that has been labeled Web 2.0. However, in my mind, the Web Services documented by Joe and Sean in 2003 is closer to an Architectural strategy encompassing Service Oriented Architecture than a social Web 2.0 strategy.
I know that there has been a lot of debate surrounding the differences and strategies between Web 2.0. SOA, and Enterprise 2.0 however, Businesses and large Enterprises take a guarded approach to sharing and manipulating data and that is why I see Web Services as more of an architectural strategy aligned with SOA as opposed to a social open strategy aligned with Web 2.0. I do think that the front end components of SOA could incorporate Web 2.0 characteristics and see Web 2.0 as a part of SOA and not a seperate entity.
In 2003, Joe and Sean identified Web Services as a revolutionary breakthrough technology. After talking with Joe this past week he mentioned that Web Services and SOA is an evolutionary technology.
I agree with Joe.