Is it possible to store objects in memory for even faster cache storage than Redis or Memcached?

Question

In-Memory storage requires serialization / deserialization when storing complex objects such as a C # POCO object.

Can't you just store the data in the cache in memory as an object graph and eliminate this bottleneck? After that, the cached and serialized data is still stored in memory, so why not save the original objects in memory for the maximum possible cache (and perhaps use Named pipes to implement a distributed cache?)

thanks

Answer 1

Waescher , , . , , , Redis/memcached. , concurrency (.. , , ). , .

, , - , . . / (, - 8- ) .

, , / / .

Answer 2

, , . () , ..

Redis Co. ( ), , Redis .

: , . , .

Answer 3

, In-Memory, . .

:

• .
• ( ) .
  • MapReduce Distributed Cache , .

• , .NET( )
• .
• , ,
• ( )

, , , . ,

Understanding these pros and cons, most or all distributed caches choose to serialize even when the caches are stored in the process. Serialization is also not so high when we consider most use cases.

In addition, the @Waescher dot is also true when the network is involved, all data types must be converted to bytes for transmission.