Home > Articles > Programming > Java

The Web Services Shootout: .NET or Java?

  • Print
  • + Share This
Without being distracted by the "Java versus .NET" din, developers who haven't yet committed to Web services can attack the problem intelligently by comparing apples to apples. Blake Watson examines how you'd accomplish the same task using each of the competing technologies.
Like this article? We recommend

Introduction

For years, when customers have asked me for "Web-based solutions," I've had to nail down the specifics: What problem do they expect to solve? In many cases, all the customer really wanted was a client/server application in which the client could hook to the server through TCP/IP. I'd build a couple of native applications and get the benefits of Internet connectivity without forcing the customer to use a crude Web-based interface.

Technically, this approach doesn't create a Web service because it doesn't use WSDL (see sidebar). If you're a programmer who has had the same type of experience—building client/server apps connected through the Internet—you probably want to know what you gain (as well as lose) by building a "real" Web service. Then you'll have a technical grounding for answering the question "Java or .NET?"

What Exactly Is a "Web Service"?

.NET and Java are synonymous in most people's minds with Web services, especially those who don't really know what a Web service is. You can find definitions of the term Web service—all different—in several articles here on InformIT. These articles are different angles on the same elephant, but the one most relevant to our discussion is in the article "Describing Web Services: WSDL," by Eric Newcomer: A Web service is an application that uses the WSDL standard to provide functionality and to make itself knowable. (Not actually known, mind you, but knowable through a directory service of some sort.)

  • + Share This
  • 🔖 Save To Your Account