What is Web API? Basics

https://is1-ssl.mzstatic.com/image/thumb/Podcasts113/v4/b8/b4/05/b8b4053e-94a9-82e8-2ba2-b4c1935eb561/mza_2297191724307877965.jpg/600x600bb.jpg

Dotnet Bees

Prashant Maurya

6 episodes

6 days ago

Hey Everyone, My name is Prashant Maurya and I have started this podcast to help aspiring dotnet developers to achieve big into dot net development. As a listener you will be getting latest dotnet updates, tips and tricks and many more related to dotnet You will also be hearing experts talking about dotnet and interview questions. Please like and share podcast to other dotnet developers Let’s learn and grow together. Thank you for listening

Technology

RSS

All content for Dotnet Bees is the property of Prashant Maurya and is served directly from their servers with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.

Technology

https://d3t3ozftmdmh3i.cloudfront.net/production/podcast_uploaded/5186813/5186813-1588540183211-293ef58ecb2cf.jpg

What is Web API? Basics | Beginners

Dotnet Bees

3 minutes 15 seconds

5 years ago

What is Web API? Basics | Beginners

Hey Everyone,

Thank you for tuning in and you are listening to Prashant where I will talk about dotnet and related Technologies.

Today I have taken up a very interesting topic called WEB API.

We will try to understand what is web API? And why it’s been brought in to the web development?

As per Wikipedia API is the Application Programming Interface for either a web server or web browser.

Before we jump into what is web API let’s try to understand how the web applications used to work before web API.

Initial days of web application development both the presentation layer and server-side code has to have in the same project.

Such tight coupling of server-side and client-side code did not allow developers to work separately. Until and unless the work of BE did not complete, the work of FE could not be started.

This tight coupling also restricted the use of multiple tech stacks into the product.

Deployment of such applications became pain since it was not possible to deploy presentation and server code into a different machine.

They had to have the same machine.

Which resulted in less utilization of server resources and increased the cost of deployment.

The major problem with such an approach was after a certain time adding new and removing Any feature from the product became very difficult.

It was hard to understand the system for new developers. All such delays and costs resulted in a huge revenue decline for software companies.

Then the concept of WEB API evolved. It promised to bring clear separation into the product code.

If someone wants to develop server-side code in dotnet core then for the presentations layer the code can be developed in any language.

It provided flexibility in choosing the tech stack and also

It can be reused in the different presentation layer. This means once the product functionality is written it can be consumed by any presentation layer.

WEB API also solved the problem of deployment where both presentation and server code could be deployed in the different cloud servers.

Web API also allowed developers of both UI and BE to work independently.

Now next question comes how WEB API able to solve this problem?

Server-side code will expose endpoint which could be consumed by the presentation layer using HTTP or SOAP

Endpoints are nothing but a URI using which any interface can consume data or post data to the server.

WEB API brought a drastic change in the way web applications used to look before.

I hope I have covered most of the things in the basics of WEB API.

Stay tuned will bring some more interesting topics for you.

Till then stay happy and keep sharing the knowledge.