If you're going the "non-default" route of using postgresql you might as well ditch PHP.
Unless P=Python? :-)
LAMP is a loaded acronym which these days basically means "a web app built using FOS but not in Java or Ruby".
Unless P=Python? :-)
LAMP is a loaded acronym which these days basically means "a web app built using FOS but not in Java or Ruby".
Am I normal?
For example: http://tagwalk.com/tag/MySQL
I hope your development is driven by accurate profiling and benchmarks. It's much better to have a dirty, but very surgical fix in a specific bottle-neck, than to have your application "scaled" with too many layers of individually "optimized" components, that bog each other to a crawl when combined.
Mono for long-running and complex backend processes.
nginx, PHP, MySQL, memcache - for presentation - quick!
node.js provides an event bus between PHP and Mono
MongoDB is taking over from storing large blobs of JSON in MySQL.
I was on the opposite side of things, when I did we last. I had language integrated into the web server, and I wrote my own caching primitives. All optimization went into the request handler, and optimizing a single function is easier than debugging a whole stack.
A decent solution, but it had no massive inputs, so I slept better at night knowing it wasn't being tested.
rails, sinatra, mysql, resque, custom email server (looking for a name...), memcached.
How the heck do you mix in mono?!?