Re:Automatic REST API for Any Postgres Database
by zentrus on Saturday January 03, 2015 @08:55PM
(#8832858)
I'm not sure if this is exactly where al2o3cr was going, but a Ruby (or whatever) application would normally include such things as caching and queueing. Despite the slowness of Ruby et al, I actually would expect a modern application with these layers to handle load much better than straight database calls. So I guess I would consider the PostgREST implementation a bottleneck because you can't add any of these layers.
[ Parent
| on HN ]
Re:Automatic REST API for Any Postgres Database
by icebraining on Saturday January 03, 2015 @09:15PM
(#8832909)
Why couldn't you add a plain HTTP caching layer (e.g. Varnish) on top of PostgREST?