News for hackers. Stuff that matters.
Re:PostgREST – REST API from any PostgreSQL database by caf on Wednesday July 22, 2015 @06:04AM (#9928638)
Presumably because browsers talk HTTP, but don't talk Postgres' native protocol.
Re:PostgREST – REST API from any PostgreSQL database by twistedpair on Wednesday July 22, 2015 @09:52AM (#9929625)
Just 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.
Re:PostgREST – REST API from any PostgreSQL database by scttnlsn on Wednesday July 22, 2015 @12:50PM (#9930763)
Yeah, 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?
Re:PostgREST – REST API from any PostgreSQL database by vkjv on Wednesday July 22, 2015 @02:13PM (#9931312)
You 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.

Re:PostgREST – REST API from any PostgreSQL database by spacemanmatt on Wednesday July 22, 2015 @07:43PM (#9933100)
Squeezing 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.

Re:PostgREST – REST API from any PostgreSQL database by elchief on Wednesday July 22, 2015 @02:07PM (#9931280)
Cuz you use GET for queries with REST