Cool article and an interesting concept. It's definitely good to think out of the box - but I've rarely had to deal with a database OOMing (I assume because they have strategies to write to disk before that happens).
There are plenty of strategies nowadays to avoid garbage collection and use-after-frees (rust comes to mind), I'm not convinced working with fixed amount of resources is the most friendly to operators.
There are plenty of strategies nowadays to avoid garbage collection and use-after-frees (rust comes to mind), I'm not convinced working with fixed amount of resources is the most friendly to operators.