Fellow blogger Loraine Lawson does a great job in filling in the missing pieces of my previous posts on Chrome's value to SOA.
"David Linthicum started this discussion with his post on Chrome. He pointed out the industry has long had a bigger dream for the browser. The dream is that one day, the browser would be used as a single user interface for delivering applications and, well, services."
- Chrome is built for the use of services, and Linthicum believes it's much better at this than your ordinary, evolved-from-content-delivery browsers.
- Chrome is a better for delivering services than an traditional OS-based interface.
- Therefore, Chrome is a better platform for mixing and matching applications, services, and processes.
- Thus, Chrome will make it easier for businesses to see services in action, whether they're internal or delivered via the Web."
"By George, I think she's got it!" Actually I did not go into a good, direct discussion around the technical attributes of Chrome because so many other bloggers and authors where covering it, but I think I should have, based on the questions and comments I received. In the world of blogging, you hit on something with less than 300-400 words and move on to something else. This is actually a great topic for a feature article… hint, hint… wink, wink… nudge, nudge.
Of course not everyone agrees with me. Indeed Rob Eamon, in his comment on my and Joe's postings, pushed back on Chrome as related to SOA.
"The tenuous tie between SOA and a specific browser would seem to muddy the waters as far as what SOA really is. Alas, the ship seems to have sailed and the days of treating SOA as a way of structuring an architecture instead of as being about specific technologies are long gone."
Well, if there is anyone who says "SOA is something you do, not something you buy" (or download), it's me. However, it does not mean that specific technology can't come along that provides a good systemic tool that will make service visualization and use easier. That's my point. It's not a savior for SOA, as I said in my last post. Just cool technology that makes some aspects of SOA within some specific problem domains easier to solve. Technology is never something that drives architecture; it's the other way around. So, I agree with Rob on that point.
Good discussion around this topic. I'll pick it up again as we understand more about Chrome.