ASP.NET MVC

You can follow my article on this

https://www.sharpencode.com/article/WebApi/implementing-crud

Thank You So much

Hello Jaya,

Both the way is good for beginners. But I would suggest to go with Web API. there are several advantages as mentioned below:

• It’s simple, scalable, and robust because it supports all the MVC features such as routing, controllers, model binders, IOC container, action results, filter, or dependency injection as it is built on top of Asp.Net MVC.
• Empower the developers by handing over control over the way HTTP protocol messages are sent and responded to.
• Unit testing is easy as it supports test-driven development.
• It provides ample flexibility in web API creation due to content negotiation and drives support for the ASP.NET routing.
• Unlike WCF REST services, there is no need to define tedious configuration settings for different devices.
• The architecture of web APIs is very light, which makes them a perfect alternative for developers when they want to build applications for devices with limited bandwidth.
• Web APIs are used to create non-SOAP-based HTTP Services, so if there is a requirement for web services, but not SOAP, then ASP.Net Web API is great to look for.
• Supports different message formats like JSON, plain text, and XML.
• Asp.Net Web API supports convention-based CRUD Actions since it works with HTTP verbs GET, POST, PUT and DELETE.

And also I can say development wise it's new technology.

Thank you