July 2017
Beginner to intermediate
358 pages
10h 54m
English
With RPC you do not have the luxury of using HTTP verbs to confer the intent of the API, for example, you have the collection users. With an HTTP API you would be able to split up the various actions using GET, POST, DELETE, and so on. This is not possible with an RPC API and you need to think in the same way as if you were writing methods inside your Go code, so for example:
GET /v1/users
The preceding code might be written as an RPC method as follows:
Users.v1.Users GET /v1/users/123434
Alternatively, it might be written as an RPC method as follows:
Users.v1.User
Sub collections become a little less semantic, whereas in a RESTful API you would be able to do the following:
GET /v1/users/12343/permissions/1232
You cannot ...
Read now
Unlock full access