4 ms·
Strict REST can also result in a lot more requests than a denormalized API might, and that's mobile-unfriendly.
by cauterized 12y ago
Strict REST can also result in a lot more requests than a denormalized API might, and that's mobile-unfriendly.
- dragonwriter 12y agoStrict REST doesn't require normalization; there is nothing in the definition of the REST architectural style that prohibits resources that are aggregates of -- in DB terms, equivalent to whole tables, or rows from a complex view, or whole complex views -- of other resources, and allowing those derived resources to be directly retrieved or manipulated (with the latter also affecting the "base" resources.) The kind of REST that simply maps resources to DB rows with collection resources for base tables and does nothing else is naïve REST, not particularly any stricter REST than more complex and application-suited resource models.