- The high performance of frontend combined with high performance backend make for an awesome user experience.
- Non-blocking web servers are just cool! Actual I have blogged about this a lot but it really comes down to efficient resource utilization and simplified programming model.
- Scalable data storage system. This I have also blogged about how RDBMS are quickly flawed for scaling even a small volume of web traffic.
- As these are my favorite tools that I call myself an "expert" (and expect to get paid to consult for them) I should put them together to see what the issues are.
I wrote a non-blocking web server and I am not even using it (shame shame shame). The truth is I was looking to try and us a non-blocking (async) library for Python and I found it here. The code better utilizes the operating systems non-blocking apis like epoll on Linux and kqueue on BSD. The problem is that I quickly figured out the code base was just so much better than what I was had. The only real problem is that they didn't support some of the features and WSGI in a way that I would have liked. I will probably create a little project to do this but that is for another blog. I already have made some improvements in my clone. So not only do that have a simple non-blocking API for the servers side but they have a good one for using as a client (will talk about this later).
In summary I am very excited about this stack. It really feels like a best of bread tools for creating a rich user experience that can scale for the masses (once non-blocking Riak client is fixed). Please kick the tires and report bugs hackingthought.com.