This is the second post of the series on RESTful Web Service.
Part 1, Part 3, Part 4
In this post we discuss how to design and build a REST API (a collection of REST web service).
As with any design we ask ourselves what our end goals are, and then decide how we go about achieving these. I believe the questions below set out what the minimum end goals are when designing a successful REST API.
1. How do we discover a Resource? What is its URI? How do we map HTTP methods to the actions possible in an entity?
2. What is the representation of the resource?
3. How do we decide on a contract for the services?
Answers to question 1 and 2 are necessary for designing both HTTP and REST web service; the answer to question 3 really define how to make the service REST.
We'll cover the first two in this post, and the third in a subsequent post.
Read the full article here.
Part 1, Part 3, Part 4
In this post we discuss how to design and build a REST API (a collection of REST web service).
As with any design we ask ourselves what our end goals are, and then decide how we go about achieving these. I believe the questions below set out what the minimum end goals are when designing a successful REST API.
1. How do we discover a Resource? What is its URI? How do we map HTTP methods to the actions possible in an entity?
2. What is the representation of the resource?
3. How do we decide on a contract for the services?
Answers to question 1 and 2 are necessary for designing both HTTP and REST web service; the answer to question 3 really define how to make the service REST.
We'll cover the first two in this post, and the third in a subsequent post.
Read the full article here.
