Transactions' logic should be handled on the server side (vs client == django-roa), you can't think about REST like a database model.
Right. But since a model maps to a table and in REST it maps to a list of row-like resources, then this can't be used as a drop-in replacement. With relational models you handle transactions in Django because you potentially update multiple tables in one request. With django-roa, I suppose, you'd have to structure the data accordingly. For example with xml or json fields. And then it'd be up to the server (the resource provider) to take care of the transaction. Is that the idea?