Web API was created to better replace a WebService? If not, what is the exact difference between the two and when to use one or the other?
Web API was created to better replace a WebService? If not, what is the exact difference between the two and when to use one or the other?
Take a look at these sites, they make a very interesting comparison about the difference between the web service templates we have.
In my opinion, I consider that a WebApi is also a type of Webservices but based on Rest.
The WebApi Rest scenario is simpler to deploy and if you want to make it available to a wide variety of customers (cell phone, website, etc.) this is the most practical solution in my view!
No, WebAPI is for creating web services . It uses a technique RESTful to communicate interaction points. Web service is a general technique, WebAPI is a Microsoft specific technology for dealing with web services . When you use WebAPI you are doing a web service , so there is no dichotomy between them.
In the .NET Core it is neither a separate MVC technology (see more on some questions like this , this and this ).