Keep most of the object in the cache / memory embedded in the database?

Question

It just occurred to me why not use most of the objects in the cache (memory) when starting the application.

if it's not such a great web application. Or have settings for how much I want to cache / memory.

I just think this might require having something like below 1 GB of RAM or much less.

Everything to speed up the application even more without querying the database.

Is that a good idea?

Answer 1

- , . , . , memcached.

Answer 2

- .

, . , , , ?

, , . ORM- SQL , .

Answer 3

Not so good idea, node .

.

Answer 4

, .

: , , , , /

Answer 5

. , , - . , //. , , , db ( - , ).

Answer 6

, ehCache (http://ehcache.org/)

, , .

Distribution solves the issue of persistence (if you do your stuff wrong), and disk overflow allows us to basically cache everything that was simply not possible in the cache in memory.

Of course, the implementation is not trivial for a real application, but it significantly improved our performance after the caches were boiling.