Unlike C#’s IEnumerable, where an execution pipeline can be executed as many times as we want, in Java a stream can be ‘iterated’ only once. Any call to a terminal operation closes the stream, rendering it unusable. This ‘feature’ takes away a lot of power. I imagine the reason for this is not technical. What … Read more
I’d love some some help handling a strange edge case with a paginated API I’m building. Like many APIs, this one paginates large results. If you query /foos, you’ll get 100 results (i.e. foo #1-100), and a link to /foos?page=2 which should return foo #101-200. Unfortunately, if foo #10 is deleted from the data set … Read more
I want to make my RESTful API very predictable. What is the best practice for deciding when to make a segmentation of data using the URI rather than by using query params. It makes sense to me that system parameters that support pagination, sorting, and grouping be after the ‘?’ But what about fields like … Read more
As far as I can tell each individual resource should have only one canonical path. So in the following example what would good URL patterns be? Take for example a rest representation of Companies. In this hypothetical example, each company owns 0 or more departments and each department owns 0 or more employees. A department … Read more
For example you run a GET request for users/9 but there is no user with id #9. Which is the best response code? 200 OK 202 Accepted 204 No Content 400 Bad Request 404 Not Found 27 Answers 27 I strongly oppose 404 in favour of 204 or 200 with empty data. Or at least … Read more
