Shulou(Shulou.com)05/31 Report--

This article introduces what are the characteristics of XMemcached and what aspects need to be improved. The content is very detailed. Interested friends can use it for reference. I hope it will be helpful to you.

XMemcached is a Javanio-based memcached client. It is thread-safe, simple in structure, supports all memcached text protocols and binary protocols, and has excellent performance. It also supports some advanced features, such as JMX, dynamic add and delete nodes, client statistics, and nio connection pooling.

What are the characteristics of XMemcached

Compared with spymemcached, which is also based on javanio, XMemcached has the following characteristics:

1) the API model is synchronous, and the use of asynchronous API is cumbersome. After memcached protocol joins noreply, the existence value of asynchronous model becomes even more suspicious.

2) support setting the node weight of memcached

3) support dynamic addition and deletion of nodes, which can be programmed or JMX

4) support nio connection pooling, and allow users to have more control over the network level and provide more performance optimization options

5) support client data statistics

6) support that Kestrel,Kestrel is a MQserver written by scala.

What aspects of XMemcached need to be improved?

There are two areas where XMemcached needs to be improved: documentation and the implementation of binary protocols. The documentation is very imperfect, because the energy is limited, I hope to be able to make up for a better user guide. The second is the implementation of the binary protocol, which can be improved in terms of efficiency.

In addition, on the * nix system, for the application of the same host and memcached, the use of unixdomainsocket can further improve efficiency, which is also a direction that XMemcached is going to explore. Since Java does not support unixdomainsocket, it may need to be implemented through JNI.

In communication with Cao Xiaogang, founder and CTO of Renjian.com, he talked about not only using XMemcached to connect to the memcached server, but also using it to connect to the kestrel server, which steadily supports the needs of the website. Before choosing Xmemcached, Cao Xiaogang evaluated several similar tools:

The main options are spymemcached and Cen Wenchu's memcache-client-forjava. At the beginning, we chose spymemcached. His problem is that because of using the asynchronous model, it is more tedious to use and a large amount of code; after reading the code of memcache-client-forjava, I feel that it contains some functions that should not be implemented by memcachedclient, such as client-side caching, and I am more worried that it will bring some potential problems.

Another reason for choosing XMemcached is that it has been carefully debugged for performance. Of course, one of the most fundamental reasons is that when we get in touch with developers, the developer's support is in place, the response is quick, and the code quality is very high. After the actual verification, we finally chose XMemcached.

About what are the characteristics of XMemcached and what aspects need to be improved to share here, I hope that the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.