Search code examples
.netappfabricdistributed-cache

is MS Velocity ready for production?


I wonder if anyone has tried velocity in a production environment. It is in CTP2 version right now, and we are thinking of using it. Has anyone tried it? If yes was it a positive experience?


Solution

  • My personal take on this would be that you should use Memcache till Velocity stabilizes. .net clients for Memcache like Enyim have stood the test of time and used by many.

    • Use a provider independent CacheManager
    • Implement one for memcached.
    • Tomorrow if things change and you still want Velocity, change the provider.

    After all, these are just dictionaries and your domain code should be independent of the infrastructure.

    Related: A simple CacheManager interface for C#,
    My answer to Memcache on Windows.