Nginx directly to mysql. 3 - 4 times as fast as php + libmysql

This has maintainability problems written all over it. I can't imagine a web page where you would actually gain something from this, that wouldn't be complex enough that you wouldn't need some language to deal with more complex selects/inserts. And that would mean that you would spread your logic (models?) across two totally different "platforms". One part in nginx conf file (brrr) and the other in your code. Add something like Sphinx into the mix, and you have your SQL all over the place.

In other news, computer scientists discover that evented C code is faster than PHP.

Why is it only 3-4 times faster is what surprises me. No question that cutting out the PHP interpreter and VM is going to speed things up, but only ever so slightly?

Why is this a surprise to anyone? And Nginx to memcache will be even faster... and serving static content even faster...<p>You're adding a tremendous amount of overhead with any high level language stuck in between the connect and the data source.<p>This is about as basic as it gets, not worthy of #1 item on hacker news.

I'd like to see a benchmark against PHP + mysqlnd (native mysql driver for PHP, which supersedes libmysql as of PHP 5.3)

This keeps reminding me to get off my butt and make some sort of passthrough between nginx and mongodb. Yes, I know there's GridFS development but it doesn't suit my needs.

The title of this post is a bit misleading. It's agentzh (who rocks) announcing two new plugins which have plenty of use-cases.

This is really interesting, but I wonder if there is any support for user authentication? Perhaps by combining with basic auth?

This should really speed up my website's autocompletion. Not having to load the rails stack will be a big performance boost.

So, I get it and all that, what are some real world use cases of this and the postgresql equivalent? Who's actually using these things for something other than saying how fast they are?<p>I just hope they aren't being used as public-facing JSON API endpoints and the such, since none of them seem to even consider the case of SQL injection. From a quick glance it doesn't seem that any type of parameterized query or prepared statements are available to even begin helping with that, and the "documentation" examples wouldn't be setting people off on the right foot by even limiting the location paths with strict regex's.

removing high level language in the middle is good, if you need performance, why not just use redis to server json directly, in the case you need scale up your db why not use crunchDB.

What is the code in this app written in, I don't really follow?

can this be used with PHP though?