I made it to the bottom and thought the article was cut off. Turns out, it really is that simple. (Sans the sql injection and auth stuff). Fantastic.
I thought the same thing.. page could use some whitespace at the end or a footer.
Simple API with Nginx and PostgreSQL
31–40 of 74 posts
Re: Simple API with Nginx and PostgreSQL
#32very cool, add in some lua scripting and you can get some pretty solid single purpose endpoints: http://wiki.nginx.org/HttpLuaModule maybe not perfect for a whole app but maybe depending on your goals.
Can you recommend a public repo which demonstrates use of the HttpLuaModule? [Edited to add:] Another comment mentions the Lapis framework which gives [me] a good starting point. @subs: thanks!
Hope this will help you
http://blog.cloudflare.com/pushing-nginx-to-its-limit-with-l...
This helped me setting up nginx/lua/redis setup on Ubuntu https://github.com/ehazlett/nginx-rt-log/blob/master/readme....
Re: Simple API with Nginx and PostgreSQL
#33Can this be done with redis, or memcache?
Re: Simple API with Nginx and PostgreSQL
#34This article gives a good example of why you SHOULD consider using an existing framework to create a REST API. I see no concern about authentication, authorisation, scalability, protection from SQL injection attacks, nor making the output easily parseable by third-party applications. None of these are issues you can simply say, "I'll deal with that later when it becomes a problem." They are reasons why an existing fr…
"protection from SQL injection attacks" In the module he's using, there is a postgres_escape function.. so there's no reason he couldn't have used it. http://labs.frickle.com/nginx_ngx_postgres/README
Unfortunately when defaults are inherently insecure, they lead to people building insecure systems. If every single parameterized SQL command needs to include (possibly multiple) escapes then it'll be missed in some places.
It's unnecessary anyway. It would be way better would be if the parameters were bound as named parameters. Ex:
location ~ /articles/(?\d+) {
postgres_pass database;
rds_json on;
postgres_query HEAD GET "SELECT * FROM articles WHERE id = $id";
postgres_rewrite HEAD GET no_rows 410;
}
Re: Simple API with Nginx and PostgreSQL
#35Can this be done with redis, or memcache?
There is http://wiki.nginx.org/HttpMemcachedModule, but it's not really the same thing.... Cool though.
Re: Simple API with Nginx and PostgreSQL
#36Wouldn't you be throwing away your ability to add a caching layer. I guess their are ngx modules for Memcache/Redis but coding even a simple api in nginx.conf can get difficult?
I still like the idea of nginx being able to communicate with different datastores. For example, let's say you want to serve a file but it requires authentication, you can pass some signed request via query string and cross check it in session in redis/postgres wherever.
Re: Simple API with Nginx and PostgreSQL
#37Doesn't couchdb accomplish this? (out of box REST API with little config)
Re: Simple API with Nginx and PostgreSQL
#38Pretty neat, what about SQL injections?
This example is not secured against SQL injections but you can do it easily. Look at the documentation here: https://github.com/FRiCKLE/ngx_postgres/
I would implore blog writers to not do this. I realize it makes the code easier to read, but even if you loudly disclaim "THIS CODE IS INSECURE DO NOT USE IT AS-IS" there are plenty of copy/paste coders in the world who will do exactly that, perhaps even intending to come back later and add in the protections, but never actually get around to it.
Re: Simple API with Nginx and PostgreSQL
#39Great for a quick little hack, but I wouldn't want to maintain that conf file once the project grows.
Re: Simple API with Nginx and PostgreSQL
#40Can this be done with redis, or memcache?
Same developer made this: