I apologize for the perhaps obvious question, but I just started looking in the direction of these tools. I only know that one is old and the other is new. Can a respected community explain the difference between these tools and their scope?
Thank.
I apologize for the perhaps obvious question, but I just started looking in the direction of these tools. I only know that one is old and the other is new. Can a respected community explain the difference between these tools and their scope?
Thank.
There is no product called “memcache”, AFAIK.
There is a “ memcached ” (fast key-value storage in memory), and there is a “ MemcacheDB ” (uses the memcached protocol, but stores data, if I remember correctly, in BerkeleyDB, providing persistence). Well, there are still any, using the protocol of the same memcached, Membase associates, with clustering, replication and other buns.
Guess where the legs grow from. PHP has two clients, just called one “ memcache ” and the other “ memcached ”. Actually, there is a table with a comparison of these two clients, according to it, I think everything should be clear.
| pecl / memcache | pecl / memcached | |
|---|---|---|
| First release | 2004-06-08 | 2009-01-29 (beta) |
| External dependencies | Not | libmemcached |
| Auto Key CorrectingÂą | Yes | Not |
| Add to start / end | Not | Yes |
| Automatic serialization | Yes | Yes |
| Binary protocol | Not | Optional |
| CAS | Not | Yes |
| Compression | Yes | Yes |
| Timeouts | Only connect | Various options |
| Consistent hashing | Yes | Yes |
| Deferred GET | Not | Yes |
| GET multiple values ​​per request | Yes | Yes |
| PHP session support | Yes | Yes |
| SET / GET to the specified server | Not | Yes |
| Storing numbers | Converted to strings | Yes |
Âą) When trying to SET or GET to an incorrect key, memcache converts the incorrect key to the correct one, and returns false .
Source: https://ru.stackoverflow.com/questions/38560/
All Articles