Earlier quoted context omitted.
I've been learning it recently and I'm not sure what to make of it, specifically the ORM component. It certainly has a good reputation as far as ORM's go, but I'm not sure if even a good ORM fits a large, popular, or complex app, or is perhaps more suitable for protoyping and low-traffic uses. But since SQL is pretty necessary for most web apps, it makes sense to pick some abstraction layer, and as far as I can tell…
Things I learnt, that might help. 1. You don't have to use SQL. 2. If you are going to use SQL, Find a wrapper that is minimalistic for your current needs. Work with lesser and you will work more but you will also work with more freedom and sanity. Best of luck friend. :)
Trouble is, I understand the theory of in-memory data logged to disk, but as I'm just a humble hacker (self-taught amateur) there seem a lot of unknowns in such an approach. SQL, though a pain, is at least familiar and abundantly documented.
Guess I'll do a little more research, and a little more hacking, since I would be quite happy to drop SQL entirely!