> skip the database, the ORM layer, the glue code, the data model, and all that ancillary stuff, and simply cache the ebook objects themselves
It is nice to see people thinking in this direction, instead of just assuming you need a full database if you have any data. For non-transactional key-value storage, it works well in many cases, even with 100GB+ of data.
A month has about 2.6 million seconds in it; 1.2 million page hits per month works out to half a request per second.
Dynamic web frameworks considered to be worst-in-class for performance, such as Rails, are capable of rendering basic HTML dozens of times per second on a Raspberry Pi.
Reading this article is like listening to a teenager, having successfully microwaved a plate of hot pockets, tsk-tsking the complex machinery of a commercial kitchen.
I'm not up to date with Ruby on Rails, but isn't it in roughly the same class of 'classic' web that this article describes? i.e. server side stuff delivered to the browser with minimal JS? I think it was the last time I looked at it.
6 comments
[ 4.5 ms ] story [ 30.0 ms ] threadIt is nice to see people thinking in this direction, instead of just assuming you need a full database if you have any data. For non-transactional key-value storage, it works well in many cases, even with 100GB+ of data.
I had assumed it was a CDN they were using but this suggests they may have done it by hand, which is cool.
Dynamic web frameworks considered to be worst-in-class for performance, such as Rails, are capable of rendering basic HTML dozens of times per second on a Raspberry Pi.
Reading this article is like listening to a teenager, having successfully microwaved a plate of hot pockets, tsk-tsking the complex machinery of a commercial kitchen.