WEB API Project Combat Series-navigation (full dry sharing)

The purpose of this series is to pour out the dry goods accumulated over the last two years in the practice of Web APIs and share them with you. It is also welcome to discuss communication with a friend who is using the Web API or who intends to use the Web API in the project, so that I have enough enthusiasm to complete this series.

What is the actual situation for this practice?

1. Apply to the application server-side development, mainly for the app to provide service, interact with the app, complete a variety of data exchange.

2. When the front and back end of the separation as a back-end exist, assume the responsibility of business processing, reduce the front-end business processing.

3. To provide unified data exchange for different systems, Xml,json is the most commonly used data interchange format between two systems, and the Web API provides very good support for both formats.

Special Note:

1. Because JSON is relative to XML, there is a natural advantage, and all APIs are focused on JSON.

2. The interface exposed by the Web API will refer to the RESTful specification as much as possible.

RESTful RELATED LINKS

Understanding the RESTful architecture http://www.ruanyifeng.com/blog/2011/09/restful

RESTful API Design Guide http://www.ruanyifeng.com/blog/2014/05/restful_api.html

Chapter Navigation

1. Web API 2 Getting Started
2. Interface documentation and online testing (test can be directly involved in API testing OH)
3. API exception handling and friendly error message output
4. API access authentication, authorization
5. Uploading and downloading of files
6. Continuous integration (by Jenkins)

(To be Continued ...) Welcome you to add)

WEB API Project Combat Series-navigation (full dry sharing)