Is EnyimMemcachedCore's storage/retrieval behavior compatible with EnyimMemcached?

[andrew-vant]

Context: My team is beginning to port several related programs from (EnyimMemcached/dotnet/Windows) to (EnyimMemcachedCore/dotnetcore/Linux). For at least a little while, the old and new versions will have to cooperate, and I'm trying to find out if that will be a problem. Issue #70 and its resolution suggests to me that this is supposed to work, but I'd like to be sure.

If one process stores a key and value with EnyimMemcached, and another process tries to retrieve it with EnyimMemcachedCore, will it do the Right Thing?

[gustavocarpaneses]

I´m still have a problem after Issue #70. I have the same scenario that you described. And a specific key points to one node with EnyimMemcached and to another node with EnyimMemcachedCore.

I described the problem at #70

[trungdang194]

Hi @cnblogs-dudu, I would like to ask the behavior of finding a node in EnyimMemcachedCore is it still behave like EnyimMemcached?

• Is it using consistent hashing Ketama or what type of strategy to locate node? And how about the default virtual node = 160 setting still applied to it?
• Is it using FNV1a as a default hashing algorithm and there is no way to configure other hashing algorithm?
• Is it still behave like EnyimMemcached?

[cnblogs-dudu]

@trungdang194 Please see the codebase.