This post originated from an RSS feed registered with .NET Buzz
by Udi Dahan.
Original Post: AJAX & SOA to merge? puh-lease!
Feed Title: Udi Dahan - The Software Simplist
Feed URL: http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist
Feed Description: I am a software simplist. I make this beast of architecting, analysing, designing, developing, testing, managing, deploying software systems simple.
This blog is about how I do it.
"Although technologists have been calling for the marriage of hot technologies such as SOAs and AJAX to help users better leverage Web services, the industry is only now beginning to see products that fully support this integration. At the AJAXWorld conference, JackBe and TIBCO Software are unveiling initiatives to more tightly link service-oriented architectures and Asynchronous JavaScript and XML."
First of all, as we already know, SOA is not a technology.
Second, SOA is not dependent on Web Services, but can be implemented with them.
As for integration between AJAX and SOA, from the service's perspective, anyone can send it a message, and the service will then decide based on certain criteria (policy if you will) whether or not to handle the message or send a response. So, AJAX doesn't change anything in terms of SOA. As for the ability to send a message to a service, AJAX has certain limitations security-wise since it's run out of the browser, but these shouldn't be a problem.
So, it appears for lack of anything important to do, the vendors decided to invest in integrating stuff that can already work together just fine, maybe a point-and-click interface for developers?
Previous Topic
