Why services (web) came into picture in ASP.NET ?

Question

0.00/5 (No votes)

See more:

We can implement web applications using class library to talk to database server, or to another application/APIs.

Then why we need web services??

What can be done in web services, which cannot be done in class library ??

What I have tried:

What can be done in web services, which can't be done in class library ??

Posted 3-Jan-19 10:04am

Kingshuk_SP

Updated 3-Jan-19 22:04pm

Add a Solution

2 solutions

Solution 1

APIs allow applications to interact with one another, and as a whole do not specify what communication medium or protocol is used.

A Web Service is basically a wrapper around an API which uses a computer network as the communication medium and generally uses the HTTP protocol.

All Web Services are APIs, but not all APIs are Web Services.

Posted 3-Jan-19 13:11pm

MadMyche

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Vincent Maverick Durano · Accepted Answer · 2019-01-03T22:05:00

Adding to the existing solution provided, here's my take:

Class libraries will turn into Dynamic-link library (a.k.a DLL). All consuming clients will have to add the dll to their project to reference them. This is fine if you will be dealing with applications within your premise or domain. However, if there are other client applications that want to reference your class library then it's gonna be a pain in the butt because you have to ensure that they got the right version and the proper access to your dll. With Web Services, you can simply host them in public facing server where other client applications can have access to via HTTP.

The important difference between them is that if you are working on modern web applications that heavily relies on AJAX and JavaScript and you want to communicate with your data from the server, then a class library can't do that. One advantage of the Web Services is to be able to communicate with your data via AJAX calls.