Configuring Multiple Clients → Web API → (In Memory or SQL Server)
In this scenario, WPF, ASP.NET MVC, and non-.NET clients (browsers, mobile devices, Java, etc.) directly communicate with the Web Api application via HTTP. This setup provides ultimate flexibility, allowing virtually any client capable of HTTP communications to interact with our middle tier.
In the case of the .NET clients, they consume the business services, often times preventing unnecessary round trips to the Web Api upon unsuccessful business rule validations. The Web Api application consumes these same set of business services to serve as a last line of defense against non-.NET clients.
This configuration can be accomplished by following these two configuration setup procedures:
#####WPF → Web API → SQL Server #####ASP.NET MVC → Web API → SQL Server