Architectural Issue in ASP.Net application with Web API

Question

We have an 3 layer architecture of ASP.Net application which builds with SQL back end and running in Production for last 2 years.

Now we plan to start develop Version 2 of that application by expose data through Web-API. So, we are busy creating the POC for that architectural implementation.

Problem is, we have an existing solution with 3 projects(ASP.NET+BAL+DAL). So, I planned to replace DAL with Web-API because it itself contains Models to interact with back end Database. I have created a separate solution for Web-API. In my POC, Web-API runs in separate port(ex:localhost:122) & My ASP.NET application runs in with default port(ex:localhost:80). From my ASP.NET application, while I call the Web-API controllers its not returning results. But while checking the Web-API like "http://localhost:122/api/Products" i'm getting the responses.

While seeing the sample Architectures from google, People introduce "Service Layer" in the main(ASP.NET+BAL+ServiceLayer) solution and keep calling that service layer will internally call the original(withich connects with DB) Web-API. Is that only way of doing it ?

Please correct me if my assumptions are wrong.

Davin Tryon · Accepted Answer · 2014-01-31 11:22:53Z

1

When exposing a Web API, it is best to think of it like an alternate UI. It just so happens that it is a very ugly UI (proabably JSON or XML). And it isn't very usable by average users because they would have to construct requests by hand etc.

A 3 Tier architecture is about preserving the BAL and DAL for multiple front ends. Web API is an alternate front end. So, it would seem best to reference BAL and DAL inside a new process (the Web API) and then expose it.

I'm not sure if this is the same concept as a "Service Layer" or not. That term is overloaded with many different meanings to different people.

So, I would not replace the DAL with the Web API (because it has models etc). Instead, use the Web API models (or view models) to define the alternate front end structure and map to these from existing BAL services and entities.

Hope this helps.

answered Jan 31, 2014 at 11:22

Davin Tryon

67.4k15 gold badges149 silver badges139 bronze badges

Sign up to request clarification or add additional context in comments.

14 Comments

Karthick Jayaraman Over a year ago

Yes, I can do add reference of BAL, DAL in my Web-API. But my problem is, why can't I consume data from Web-API (which runs in different port) directly in my ASP.NET application.

Davin Tryon Over a year ago

Are these calls being made from Javascript in the ASP.NET application. Or server-side?

Darrel Miller Over a year ago

@KarthickJ. Because DAL interfaces are too fine grained, they are too chatty for HTTP and they need support for transactions. HTTP just isn't optimized for that style of interactions.

Karthick Jayaraman Over a year ago

@DavinTryon - Exactly !! I'm doing Ajax call to fill my JQGrid.

Davin Tryon Over a year ago

You are probably hitting an issue with CORS.

|

Collectives™ on Stack Overflow

Architectural Issue in ASP.Net application with Web API

1 Answer 1

14 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

14 Comments

Your Answer

Sign up or log in

Post as a guest

Related