Is ASP.NET Web API good to use as a service level?

My architect and I are designing an architecture for one of our products, and he suggested going with Web Api as a service level (because it's an easy component).

Right now I’m thinking how it can be used for non-http clients, as well as for external clients. How can we provide proxy information about our API (in case the API has a complex type as a parameter)?

Consult if the web API can be used as a service level?

+4
source share
2 answers

Immediately I think how it can be used for non-http clients

, . -API HTTP. , UDP, WCF.

- API

RESTful -. .NET. .NET (Request/Response Dto) . Dtos, , -, , SOAP, REST.

+6

,

0

All Articles