Where does Web API fit in a typical n-tier architecture?

Question

Usually when i layout an n-tier architecture for a project I have the following layers:

• Domain (domain model, repository contracts)
• <

Answer 1

There could be 2 approaches:

1. You decide to consume your Web API from the MVC application through HTTP calls. In this case the calling code (HttpClient) sits in your Data layer. Whether you are fetching your data from a database or a remote web service call it shouldn't really matter. In this case since the Web API probably already encapsulate much of the business logic your service layer will be very thin, just a wrapper around the data access layer, or even non-existent if it doesn't bring any additional value.

2. Since the Web API is written in .NET you could decide to directly reference the assembly containing the service layer of this API in your MVC application. In this case the service layer of your Web API application becomes the service layer of your MVC application.

Answer 2

There are two possibilities

• Middle-tier or middleware: this is where typically web services and WCF Services have been working. Using REST is much lighter than SOAP so this is de-facto use case. Web and WCF services are better in respect to client generation but Web API will gradually catch up.
• Presentation layer: this will provide data to the Single-Page-Applications or any modern web site/application that uses data and renders on the client.