Well, redis is "eventually persistent" that it means it works in memory but it can perform disk write according with configuration (e.g. after 10 update in 300 seconds or whatever you want) so you have in memory speed and persistence at the same time, O(1) complexity, very low overhead. In my opinion it fits better for such purpose. Cons are it is limited by memory size. I would prefer to use orientdb for its ability to keep things together and redis for its speed but I still curious on a performance comparison, of course both working in memory.
Il mer 23 mar 2016 16:29 'scott molinari' via OrientDB < [email protected]> ha scritto: > Hey Andrey, > > Interesting rocket science like stuff! Then it wouldn't be too bad > performance-wise to even use a regular database with the hash index, that > way sessions aren't volatile. Cool! > > Scott > > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "OrientDB" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/orient-database/d8a6fTsPQXQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
