Hello there gentle-people. I am one of two R&D board members at Kompiler.no, and in this post I want to give a brief look into the stack driving the Kompiler.no site. If you are into web stacks this might just be the post for you!
At this point you might ask yourself why we would change the stack. Why change something if it just works ™. I believe one of Kompiler's core missions should be that of providing a learning environment. One should not be afraid of testing out the new and shiny, so here is kompiler.no in all its new and shiny bravado.
The Apache HTTP server software has driven a lot of web servers for a long time. It is however not generally asynchronous and will spawn new threads for every request. Not really a problem for a site the scale of kompiler.no, but no less a less than optimal design. Further I feel configuration of Apache leaves a bit to be desired. Nginx seems light weight in comparison, provides single-threaded (you can have multiple workers) asynchronous serving of resources, and configuration is generally a breeze.
Software aside, you might wonder what kind of hardware we're running on. With the risk of triggering the buttcloud plugin in your browser I can inform you that we host our Kompiler.no server in the cloud. It is an SSD backed server with ample memory (1GB) provided by DigitalOcean. But all traffic is routed through Cloudflare to minimize the response time on our servers.
In conclusion I think we can safely say that the stack is way overkill for something the size of Kompiler.no. But were is the fun in a shared LAMP server with php and MySQL backed applications? I see none, and that is why we now enjoy the LNSJ-stack on a dedicated VPS.