Disadvantages: You need to learn how to set up GraphQL. The ecosystem is still rapidly evolving so you have to keep up. You need to send the queries from the client, you can just send strings but if you want more comfort and caching you’ll use a client library -> extra code in your client … Read more
In my experience, GET /users/{id} GET /users/email/{email} is the most common approach. I would also expect the methods to return a 404 Not Found if a user doesn’t exist with the provided id or email. I wouldn’t be surprised to see GET /users/id/{id}, either (though in my opinion, it is redundant). Comments on the other … Read more
gRPC is not really the relevant part for comparison, it’s that gRPC uses HTTP/2 which can certainly be compared to WebSockets. https://www.infoq.com/articles/websocket-and-http2-coexist This article outlines them quite well. Essentially, HTTP/2 is Client/Server with Server Push on the background, so you can make your request and simply stay on that connection listening for updates without the … Read more
Unauthenticated users We do a PUT request on a api/v1/account/password endpoint and require a parameter with the corresponding account email to identify the account for which the user wants to reset (update) the password: PUT : /api/v1/account/password?email={email@example.com} Note: As @DougDomeny mentioned in his comment passing the email as a query string in the url is … Read more
The reason you get no hard answers is because there is no hard RESTful standard. So I can only suggest that you create a hard standard and stick to it within your own APIs I used this as a guide for RESTful services http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api It says respond with a 204 status and an empty body … Read more
If you are passing all your parameters on the URL, then probably comma separated values would be the best choice. Then you would have an URL template like the following: api.com/users?id=id1,id2,id3,id4,id5
Its not an implementation in the sense of running code, but I really like the article “How to GET a cup of coffee” on InfoQ. It describes the process of ordering a coffee at Starbucks as a RESTful protocol. This goes beyond the typical “everything is a resource” REST introductory article and focuses on HATEOAS. … Read more
I guess your cross posted this questions to Amazon S3 forum, but for the sake of others I’d like to post the answer here: If there is only ever one “user filename” for each S3 object, then you can set the Content-Disposition header on your s3 file to set the downloading filename: Content-Disposition: attachment; filename=”foo.bar” … Read more
Nobody in the REST community says REST is easy. HATEOAS is just one of the aspects that adds difficulty to a REST architecture. People don’t do HATEOAS for all the reasons you suggest: it’s difficult. It adds complexity to both the server-side and the client (if you actually want to benefit from it). HOWEVER, billions … Read more