4 ms·
> The place where REST falls down, really, is transactions. I don't agree. The standard way of supporting transactions with REST is to provide a transactions e
by geezerjay 8y ago
> The place where REST falls down, really, is transactions.
I don't agree. The standard way of supporting transactions with REST is to provide a transactions endpoint where clients start a transaction by POSTing a new transaction resource, POST their DTOs to build up a unit of work, and when they are done just commit the transaction. That's pretty much a one-size-fits-all solution as that's the standard way to implement transactions at the database level.
- dustfinger 8y agoI was going to say the same thing and was pleased to see that someone beat me to it. If you combine unit of work pattern with continuation tokens then you can handle bulk transactions involving very large numbers of records with a simple rest interface.
- cryptonector 8y agoYes, and I've said as much. But the user-agents can't construct this without JS.