I don't get this. As fast as static blogging is, in-memory applications:<p>1) will actually beat static files in speed<p>2) you lose none of the flexibility of databases. In fact, because your effective query impact is going to be much smaller, you gain. Not in what can theoretically be done, but in what can be done practically without impact on response time, you gain a lot. Also expressivity gains (SQL is good, but it doesn't match general programming languages) (e.g. drawing a graph of "this person replies to this person and never replies to this other person" would be feasible).<p>I suppose there's problems too:<p>3) you lose that your state is always on-disk. In other words : there's a chance that you/your developer will get it wrong, but you won't notice it until your process restarts, which can be months.<p>4) of course, you have to start monitoring memory usage in these kinds of scenarios.