We're considering using OrientDB as a Web Session Cache (similar to how you might use memcachd or Redis, for example), but since we already have OrientDB "in the stack", the idea was to not introduce yet another technology if we didn't have to. I know all the "good reasons" why memcached and especially Redis are used for caching, so I'm interested to know if anyone has any direct experience using OrientDB for this purpose, as well as "any reasons not to use OrientDB for this"? --Eric
-- --- 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.
