I've been building things with web technologies professionally for a little more than 11 years now. In that time, I've used a variety of technology stacks with varying degrees of success and comfort. While at university, I was making use of the faculty infrastructure and so was building the simplest of sites on top of Apache on their unix environment. Then as I moved into developing Web applications for a living, I found myself working on Windows NT servers with IIS and ASP. Later on I moved into using the LAMP stack, which after the initial shock to the system, was a revelation and I have never looked back.
This combination of Linux, Apache, MySQL and PHP is a tried and tested technology stack which is powerful, available and free. No wonder then, that it has become the first choice of so many web developers. I've seen a swing in the default technology stack from Windows over to LAMP and have become comfortable in the LAMP world with it's GUI free interfaces, consistent and repeatable operations through SSH and so on.
Through the work that we are doing with NodeJS, we are adopting a common usage pattern. NodeJS can provide its own http server, and we tend to have several NodeJS projects being served on a single box. These can all make use of different versions of NodeJS if necessary (via the handy nDistro distribution model) each publishing on its own port. We then proxy requests to those NodeJS servers through either Apache or Nginx. This brings me to my point. A stack that I now commonly employ looks less like:
and more like:
- Not Windows
I'm not just trying to be antagonistic by stating "Not Windows". Yes, this is a conceit in order to wangle nnnn or 4N or whatever, but the real point is that all of the pieces of the puzzle work beautifully on various flavours of Linux, Unix and OSX. Windows, less so. I'm going to be using this '4N' stack for more an more projects now, and as some big players start taking a more serious look at using Node and Nginx, I think that it will become more and more common.