All geek questions in one place

The best strategy for moving data between physical layers in ASP.net

Creation of a new ASP.net application and planning for dividing the database, service level, and Web / UI layer into separate physical layers.

What is the best / easiest strategy to move serialized objects between service level and user interface level?

I was considering the possibility of serializing POCOs in JSON using simple ASP.net pages for mid-level maintenance. This means that the UI / Web layer will request data from a web server (hidden to an external user) that will return a JSON string. Such a JSON issuer seems easily verifiable. It is also easily compressed to efficiently move data across the WAN between layers.

IIS Asp.net UI webforms ^ ^ -- WAN -- ^ ^ IIS Asp.net webforms to generate JSON ^ SQL Server

I know that some people use .asmx web services for this kind of tasks, but it seems that with SOAP there is excess overhead and the package is not as human readable (verifiable) as POCOs serialized as JSON. Others use more sophisticated technologies, such as WCF, which we never used.

Does anyone have any advice for choosing a method for moving data / objects between a data layer (db) and a web interface (WI) layer over a global network using .net technologies?

Thanks!!!

+4
source share
1 answer

It looks like you want to use the REST API. ASP.NET MVC controllers will do the trick.

+2
source

Source: https://habr.com/ru/post/1305822/

More articles:


All Articles