Should I be prepared to "mix and match" languages in a Web services environment?

Should I be prepared to "mix and match" languages in a Web services environment?

With all the different platform options out there, should I look to set-up a Web services environment that is all based on one language or should I be prepared to "mix and match" languages?

    Requires Free Membership to View

    Login

    When you register, you'll begin receiving targeted emails from my team of award-winning writers. Our goal is to keep you informed on recent service-oriented architecture (SOA) and SOA-related topics such as integration, governance, Web services, Cloud and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSOA.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSOA.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

You shouldn't have to be prepared to mix and match languages--Web services shield you from having to commit to a single language. That's the beauty of Web services--they interoperate across platforms and programming languages. Good thing, too, because the chances that your Web services-based systems will all be in a single language are zero. Remember, in the federated, heterogeneous, distributed world of Web services, you'll surely need to tie in other business units, partners, legacy systems and so on.

This was first published in September 2002

Back to top