What is Memcached?
Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.
- Free & open source
- high-performance, distributed memory object caching system
- generic in nature
- intended for use in speeding up dynamic web applications by alleviating database load
Definition from wiki:
Memcached is a general-purpose distributed memory caching system. It is often used to speed up dynamic database-driven websites by caching data and objects in RAM to reduce the number of times an external data source (such as a database or API) must be read.
Who uses Memcached?
Run memcached on one or more hosts and then use the shared cache to store objects. Because each host’s RAM is storing information, the access speed will be much faster than having to load the information from disk. This can provide a significant performance boost in retrieving data versus loading the data natively from a database.
Also, because the cache is just a repository for information, you can use the cache to store any data, including complex structures that would normally require a significant amount of effort to create, but in a ready-to-use format, helping to reduce the load on your MySQL servers.
What is Memcached?
It is component which stored the data temporary for 1 Hour/ 6 Hour/1 Day etc. When we integrate the Memcached with our application, performance of application increased.
Memcached is open source, high-performance distributed memory object used for caching so that execution can be enhanced at nth level.
Where Memcached can be used?
• Social Networking -> Profile Caching
• Content Aggregation -> HTML/ Page Caching
• Ad targeting -> Cookie/profile tracking
• Relationship -> Session caching
• E-commerce -> Session and HTML caching
• Location-based services -> Data-base query scaling
• Gaming and entertainment -> Session caching
Why use Memcached?
• Speed up application processes
• It determines what to store and what not to
• Reduce the number of retrieval requests to the database
• Cuts down the I/O ( Input/Output) access (hard disk)
In what condition does retrieving cache fail?
• Memory allocated for the cache is exhausted
• Item from cache is deleted
• Individual item in the cache is expired
What is the drawback of Memcached?
• It is not a persistent data store
• Not a database
• It is not an application specific
• It cannot cache large object
Give more details about memcached failures
Memcached servers are indeed independent of each other. Memcached server is just an efficient key-value store implemented as in-memory hash table.
What makes memcached distributed is the client, which in most implementations can connect to a pool of servers. Typical implementations use consistent hashing, which means that when you add or remove server to/from a pool of N servers, you only have to remap 1/N keys.
Typically keys are not duplicated on various hosts, as memcached is not meant to be persistent store and gives no guarantees that your value will persist (for example when running out of assigned memory, memcached server drops least recently used (LRU) elements). Thus it’s assumed that your application should handle missing keys.