4 ms·
Presumably because browsers talk HTTP, but don't talk Postgres' native protocol.
by caf 11y ago
Presumably because browsers talk HTTP, but don't talk Postgres' native protocol.
- twistedpair 11y agoJust don't forget to secure it. Reminds me of when people thought it was a good idea to expose the REST API of ElasticSearch directly as their API and then got p0wned. Using "REST as an abstraction layer" isn't the same as taking someone else's OTC API, calling it your own, and exposing it to the public.
- scttnlsn 11y agoYeah, this seems great if you want to completely eliminate the middle tier and have a client application talk directly w/ the database. I'm curious why there's an entire query API via query string parameters. Why not just expose a single POST /query endpoint where you can send some SQL?
- elchief 11y agoCuz you use GET for queries with REST
- vkjv 11y agoYou can take advantage of browser and CDN caching with a GET but not with a POST. Throw in ETAGs and you can do a lot of cool stuff to make things scale really well.
- deleted 11y ago[deleted]
- spacemanmatt 11y agoSqueezing the middle tier as flat as possible is my actual strategy and goal in many distributed environments. That's totally feasible with modern tools. But sending SQL from the client is dangerous, and in this forum you'll get some interesting looks suggesting that.