Redis Java operation, comparison with Memerche

1. Jedis operation methods mainly include key, String, list, set, SortedList, hash, etc., refer to the blog: http://www.cnblogs.com/edisonfeng/p/3571870.html

2. This article focuses on the comparison between Jedis and Memerche.

2.1 Jedis is persistent with complex data manipulation types, including list, hash, etc., and the core of Jedis is multithreaded and supports slicing connection pool objects

2.2 Memerche is a non-persistent memory database, only the basic operation of the key, value type, the value type is object, its kernel is single-threaded operation, does not support tile connection, in the case of multiple JVMs we need to do the connection pool processing.

2.3 Memerche is more efficient than Jedis when it comes to operating simple business logic caches, and it is more appropriate to use Redis if the data types required for complex business require finer granularity, plus It is recommended to use Redis if you want to build a distributed cache service and for scenarios where the stability of cached data is high, and Memerche is recommended for small project prioritization and lower server cost overhead.

More than 2.4 is a little part of their own understanding, to really harness and rational use of a technology need to learn in depth the core principles and mechanisms of Jedis and Memerche

Redis Java operation, comparison with Memerche