Timeline for How to implement a partial resource rest api?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 22, 2019 at 12:19 | vote | accept | fluminis | ||
| Apr 3, 2019 at 5:16 | comment | added | Doc Brown |
If your database would only contain fields "first_name,address/city", the converter would automatically return what you specificied above, right? So it appear to me the only thing which is required here is, at the step "call a service with that parameters to do a SQL request", is to replace a SELECT * by a SELECT first_name, city ..., I guess? Or did I miss something?
|
|
| Apr 2, 2019 at 11:09 | comment | added | Laiv |
If you do partial resources querying, is mainly for performance. Right? Maybe, as GraphQL, to fit the responses to specific needs of the views/screens on the client-side, what reduce the size of the responses too. So, where do you think is going to be more performant the "projection" of fields? On DB or in-memory? Where is more complex to implement? I think making the projection in the DB is more common, easy and performant. But it depends on your stack. For example, with NodeJS this is easier to do in memory than in Java cause of the strong typing of java
|
|
| Apr 2, 2019 at 10:36 | answer | added | Ewan | timeline score: 2 | |
| Apr 2, 2019 at 10:25 | history | asked | fluminis | CC BY-SA 4.0 |