MySQL + memcache (d)

Nosql has been very popular recently because of its excellent performance in K/V Storage, which has spawned many products, such as memcached, MongoDB, redis, and TT. however, they all have some defects, such as spof and data security persistence. However, with the new technologies and ideas being productized on MySQL, these things will be gradually replaced, and MySQL will return to her kingdom. Before that, I said that memcached will be replaced by MySQL + handler socket. Now the situation has changed. to be compatible with a large number of existing memcache clients, replace the handler socket with memcached, the following architecture appears:

MySQL + InnoDB with memcached

MySQL + InnoDB with memcached has many advantages:

• Make full use of the existing memcache client to reduce applicationsProgramChanges
• Solved the problem of data storage persistence that memcached does not possess.
• Provides crash-safe and acid features not available in memcached, review and query support, and rich management and display tools.
• It solves the problem of data consistency between the cache and the database when memcached is used independently at ordinary times and provides higher performance.
• Reduce data redundancy, make full use of memory, and reduce hardware investment costs
• While providing efficient k/V Access, it also provides review query functions, such as sorting and join.

Conclusion: MySQL + InnoDB + memcached will subvert many of the original multi-layer cache architectures. The new architecture can provide higher performance and stable storage and access services, greatly reduce development complexity and hardware costs.

In addition, MySQL cluster + memcached mentioned at the MySQL user conference last year, MySQL cluster 7.2 has begun to integrate memcached, and will give full play to the inherent advantages of MySQL cluster design (K/V + sharding ), currently, the number of test data (implemented by ndbapi) has reached 2 million +/second Write Performance (8 servers) and 1000,000 RPS (read, 2 servers ). Architecture diagram:

MySQL cluster with memcached

conclusion: the future of MySQL cluster is worth looking forward. Similarly, we can imagine that in the future, only MySQL databases will be used in the system background, and SQL and nosql functions will be provided at the same time, reducing system complexity, management and maintenance costs, development complexity, development cycle, and costs, hope ......