Do I need to change my code to migrate from Memcached to NCache?

No, you don't need to change your code to migrate from Memcached to NCache. By using the NCache Memcached Client Plug-in, you simply replace your Memcached client DLLs with NCache-equivalent libraries. All API calls are mapped internally, requiring no code changes.

Why is the Plug-In approach better than the Gateway approach?

The Plug-in approach is faster because it runs in-process with the application and communicates directly with the NCache cluster, eliminating the extra network hop required by a Gateway proxy.

Memcached Client Plug-In for .NET [Deprecated]

NCache Memcached Client Plug-In for .NET allows a seamless, no-code-change migration from Memcached to NCache by providing drop-in replacements for popular libraries like Enyim, BeIT Memcached, and the .NET Memcached client. These plug-ins internally map Memcached API calls to equivalent NCache operations, enabling high-performance distributed caching without requiring application recompilation or source code modifications.

Memcached Client Plug-In for .NET

Recommended Approach to Migrate From Memcached

It is generally recommended to use a plug-in approach instead of a gateway. A gateway induces an extra network/process hop, whereas this plug-in becomes part of the client application process and directly talks to the NCache cluster using the NCache API. Thus, it results in better performance.

Memcached Client Plug-In for .NET [Deprecated]

Recommended Approach to Migrate From Memcached

See Also

Contact Us