Geek Answers Handbook

Recommendations for writing a .NET-based RESTful API

Earlier this year, the fearless StackOverflow people worked hard to provide us with the StackExchange universe API. They did it the way they did the rest - taking great care to ensure that the API was bulletproof and well designed.

I am starting a project to write an SaaS-based ERP system, and it seems that a public API is a likely future requirement for application integration. Jeff and company clearly explained in discussions about StackApps that writing a good public API is difficult.

My question is:

What things should you consider when writing a public RESTful API, especially on the .NET platform?

+4
source share
1 answer

The first decision you need to make is if you really want to create a RESTful system or want to create HTTP-api. These are two different problems.

I have been creating a RESTful ERP system in the last four years, and this is not the same as just creating an integration API.

If you want to create a RESTful system, the design of your media types and link relationships will be the most important part of the process.

+1
source

More articles:


All Articles