4 ms·
If you're putting REST in front of your database, you're gonna have a bad time. Performance suffers, and transactionality is a non-starter. Best to forego thi
by whatnotests 9y ago
If you're putting REST in front of your database, you're gonna have a bad time.
Performance suffers, and transactionality is a non-starter.
Best to forego this style and instead go with more of an RPC system.
- ruslan_talpa 9y agoI am guessing you did even look an how PostgREST works :)
- rattray 9y agoFor the lazy, would you mind summarizing? EDIT: actually, after a few minutes on their docs page, I'm still not sure "how it works" regarding perf, so this could be useful even for the not-so-lazy :-)
- ruslan_talpa 9y agoWriting docs is hard ... You can think of PostgREST as one big pure(ish) function It translates ONE http request to ONE SQL query and executes it in a transaction (after setting some context). There is very little overhead. 90%+ of the time of a request is consumed by the db running the query. So usually, a request is about 5ms-10ms (without network time).
- rattray 9y agoInteresting. Thanks for explaining!
- whatnotests 9y agoYes, I didn't even click the link.
- avelino 9y agoExist issue to support RPC https://github.com/nuveo/prest/issues/18 https://github.com/nuveo/prest/issues/18