4 ms·
I think the main problem people have with this, is that REST is not necessarily easy. And easy sometimes wins over 'good'.
by treve 12y ago
I think the main problem people have with this, is that REST is not necessarily easy. And easy sometimes wins over 'good'.
- dyoder 12y agoyou're absolutely right. and i'd be fine with that if the objection was just that: this is too hard to implement, or we don't have time, and so on. it's the rationalizing that's annoying. and obviously DropBox has the resources to implement whatever design they choose.
- cauterized 12y agoStrict 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.