There were more responses around my post yesterday than I expected. Most of the posts and articles reflecting my thoughts that Google Chrome seems to be a good step in the right direction for SOA. I'll let the reactions speak for themselves:
Joe McKendrick took did a great job of summing up the issues in his post yesterday.
"But to look at it from an enterprise perspective, Chrome may help lay the groundwork for a smoother path to service oriented architecture as well."
Also, a good summary from Richard Koman, "Chrome Will Enhance SOA in the Enterprise." Richard sited my blog post and other sources.
"Google Chrome may be the fastest browser around, but it may actually prove to be even more important to the enterprise for its ability to interact with service-oriented architectures (SOA)."
"Salesforce.com, a Google partner, is especially enthusiastic about the potential for Chrome to improve adoption of Web services. 'As we are increasingly dependent on Web apps, how business users use Web browsers changes,' said Adam Gross, VP of developer marketing at Salesforce."
But the best responses always come from comments left by the readers.
Steven Kahn, had the best comment, further stressing the technical reasons why Chrome is a good thing for SOA:
Which was my point, and covered already in many other blogs and articles. But good to say it again.
Just to be clear. Chrome is not a savior for SOA/WOA. Its value is that it considers the use of Web delivered applications, and Web-delivered services, within the architecture of the browser. It's not an afterthought. This is a huge shift in thinking, and something that is desperately needed as we drive toward the use of services for applications and composites where the browser plays a key role. In essence, Chrome will become a valuable piece of the architectural puzzle, perhaps a missing piece.