ASP.NET Core App - Web Service - Architecture Guidance

Sri Ram

6y1.1k.NET

We have a plan to implement a web app using ASP.NET Core MVC/SQL Server(using ADO.NET) and host in MS Azure Platform.

Our client wants to have web service feature to implement all CRUD operations for this web app, since client might not deploy the database on Azure and would prefer regular deployment to PROD environment. However, the web app and service are being planned to host in Azure - IIS.

When we plan to keep all data access logic in web service, what would be the best option for this scenario? Going for WCF Service or Web API?
What would be the best solution architecture for both web app and service? (e.g. case1: A service method would return an object of a custom class and this class definition should be understood by the receiving web app).
Do we need to keep the service project within the same solution of ASP.NET Core web app project or separate it to a different solution?

Experts, could you please provider your suggestions?

4 Replies

Know the answer? Post it — somebody with the same question will find it here.

Viswanatha Swamy6y ago
Accepted answer
Sri Ram,

Good morning. Below are some of the thoughts.

1. It will be better to create a .Net Core 3.1 (LTS) Web API.

2. Is your Web App (ASP.Net Web Forms, ASP.Net MVC, Angular, Vue)? The one thing we should focus on is the contract between the Web App and Web API. Example: What each form will send to Web API, and What is expected as output. How to protect your Web API? How to retrieve the JWT Token from your Identity Service?

3. It is better to have two separate solutions. That will help in building the Build and Release pipelines. We can deploy the changes to Test/Stage/Production.

Many thanks.
Sri Ram6y ago
Hi Puneet,

Thanks a lot for your input.
Sri Ram6y ago
Hi Viswanatha,
Thank you so much for your inputs and sorry for my delayed response. I was not keeping well and got tied up with some personal work.

Our Web app is an ASP.NET Core MVC project with .Net Core 3.1 as of now.

Our web app will typically call the Web API methods to retrieve some app data, insert/update/delete transactions data or do some validations. This Web API will be connecting to SQL Server database using the standard ADO.NET and not using Entity Framework.
Can you please provide some references or throw lights on how to protect the Web API service?

We would like to enable Web API to process/return data only when it is being consumed from our specifi web app and not with any apps/clients.

Thanks in advance.
Puneet Kankar6y ago
Hi SriRam,

I would suggested to create project with Webapi core and Angular project like given below high low structure.
WebApi Structure
-->Controllers
HomeController
-->Models
HomeModel
--> Repository
RepositoryClasses
-->Service
Iservice (interface)
--> DataAccess
dbContext
UI Angular App
Src
app
-->services
-->components
-->modules
-->pipe
app.module
app.component
app.html