tag:blogger.com,1999:blog-9203557.post114647778743914752..comments2023-09-27T14:38:58.735+01:00Comments on Mark Little's WebLog: Web Services, interoperability and portabilityMark Littlehttp://www.blogger.com/profile/15072917010265365428noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-9203557.post-1148902694737554532006-05-29T12:38:00.000+01:002006-05-29T12:38:00.000+01:00Hi Mark,Maybe you've seen this; maybe you haven't,...Hi Mark,<BR/><BR/>Maybe you've seen this; maybe you haven't, but here's <A HREF="http://atownley.org/2005/11/in-search-of-portable-interoperability/" REL="nofollow">my thoughts on portability and interoperability</A>. The extremely short version is that I think it's in everyone's interests to try and get their vendors to use portable, existing API specifications where possible to implement the emerging Web services specifications.<BR/><BR/>Contrary to what vendors would like to think, there's no guarantee that they will be the best fit for your business objectives next year or even next week. Another point for consideration is the alarming rate of acquisitions and obsolescence of technologies and/or implementations in the current marketplace. Any enterprise or system architect worth their salt should be paying attention to these things when they select vendors so they understand the tradeoffs involved. Maybe it is worth it to meet a tactical business objective, but part of the point of having an architecture is having some idea of how it will evolve over time. This evolution shouldn't be driven by the technology choices you make today or be driven by the business objectives, fates and fortunes of the vendors you choose.<BR/><BR/>Cheers,<BR/><BR/>astAnonymousnoreply@blogger.com