Elasticache client - Memcached 

memcached is a fully featured Memcached client for Node.js. memcached is
built with scaling, high availability and exceptional performance in mind. We
use consistent hashing to store the data across different nodes. Consistent
hashing is a scheme that provides a hash table functionality in a way that
adding or removing a server node does not significantly change the mapping of
the keys to server nodes. The algorithm that is used for consistent hashing is
the same as libketama.

There are different ways to handle errors for example, when a server becomes
unavailable you can configure the client to see all requests to that server as
cache misses until it goes up again. It's also possible to automatically remove
the affected server from the consistent hashing algorithm or provide memcached
with a failover server that can take the place of the unresponsive server.

When these issues occur the memcached client will emit different events where
you can subscribe to containing detailed information about the issues.

The client is configurable on different levels. There's a global configuration
that you update so all your Memcached clusters will use the same failure
configuration for example, but it's also possible to overwrite these changes per
memcached instance.

Forked from the 3rd-Eden memcached project:

https://github.com/3rd-Eden/memcached

NEW FEATURES:
* Automatic cluster nodes autodiscovery and update through the "config cluster" option

$3

As in other databases and message queues, this module uses the ASCII protocol to communicate with
the server, which means that you can see what is send over the wire. For debugging this is easier
for both the users and the developers however this also means that SASL auth is not supported
because it demands the binary protocol.

Installation

``
npm install elasticache-client
`

Setting up the client

The constructor of the memcached client take 3 different arguments server
locations, config and options. Syntax:

` js
var Memcached = require('elasticache-client');
var memcached = new Memcached(Server locations, config, options);
`

$3

The server locations is designed to work with different formats. These formats
are all internally parsed to the correct format so our consistent hashing scheme
can work with it. You can either use:

1. String, this only works if you are running a single server instance
of Memcached. It's as easy a suppling a string in the following format:
hostname:port. For example 192.168.0.102:11211 This would tell the client
to connect to host 192.168.0.102 on port number 11211.

2. Array, if you are running a single server you would only have to supply
one item in the array. The array format is particularly useful if you are
running a cluster of Memcached servers. This will allow you to spread the keys
and load between the different servers. Giving you higher availability
when one of your Memcached servers goes down.

3. Object, when running a cluster of Memcached servers, some servers may allocate different amounts of memory, e.g. 128, 512, and 128mb. While by default all servers are equally important and dispatch consistently the keys between the servers (33/33/33%), it is possible to send more keys in servers having more memory. To do so, define an object whose key represents the server location and whose value represents a server weight, the default weight for a server being 1; so, for instance { '192.168.0.102:11211': 1, '192.168.0.103:11211': 2, '192.168.0.104:11211': 1 } distributes 50% of the keys on server 103, but only 25% on 104 and 25% on 102.

To implement one of the above formats, your constructor would look like this:

`js
var memcached = new Memcached({ '192.168.0.102:11211': 1, '192.168.0.103:11211': 2, '192.168.0.104:11211': 1 }, {update_time: 1000*2, autodiscovery: true});
var memcached = new Memcached([ '192.168.0.102:11211', '192.168.0.103:11211', '192.168.0.104:11211' ], {update_time: 1000*2, autodiscovery: true});
var memcached = new Memcached('192.168.0.102:11211', {update_time: 1000*2, autodiscovery: true});
`

$3


(Optional) Autodiscovery client configuration. Properties:
autodiscovery: false* by default.
update_time: 60000* by default (60 seconds). Time in milliseconds that indicates each time that the client must check clusters in autodiscovery mode.

$3

(Optional) Memcached accepts two option schemes. The first one inherits of all Memcached server instances
while the second one is client specific and overwrites the globals. To define these options,
Memcached server uses the same properties:

maxKeySize: 250*, the maximum key size allowed.
maxExpiration: 2592000*, the maximum expiration time of keys (in seconds).
maxValue: 1048576*, the maximum size of a value.
poolSize: 10*, the maximum size of the connection pool.
algorithm: md5*, the hashing algorithm used to generate the hashRing values.
reconnect: 18000000*, the time between reconnection attempts (in milliseconds).
timeout: 5000*, the time after which Memcached sends a connection timeout (in milliseconds).
retries: 5*, the number of socket allocation retries per request.
failures: 5*, the number of failed-attempts to a server before it is regarded as 'dead'.
retry: 30000*, the time between a server failure and an attempt to set it up back in service.
remove: false, if true*, authorizes the automatic removal of dead servers from the pool.
failOverServers: undefined*, an array of server_locations to replace servers that fail and
that are removed from the consistent hashing scheme.
keyCompression: true*, whether to use md5 as hashing scheme when keys exceed maxKeySize.
idle: 5000*, the idle timeout for the connections.

Example usage:

`js
var memcached = new Memcached('localhost:11211', {update_time: 1000*2, autodiscovery: true}, {retries:10,retry:10000,remove:true,failOverServers:['192.168.0.103:11211']});
`

If you wish to configure the options globally:

`js
var Memcached = require('memcached');
// all global configurations should be applied to the .config object of the Client.
Memcached.config.poolSize = 25;
`

API

$3

memcached.touch Touches the given key.

* key: String The key
* lifetime: Number After how long should the key expire measured in seconds
* callback: Function

`js
memcached.touch('key', 10, function (err) { / stuff / });
`

memcached.config Get nodes.

* type: String In older versions < 1.4.14, use 'AmazonElastiCache:cluster', versions >= 1.4.14, use 'cluster'
* callback: Function

`js
memcached.config('cluster', function (err) { / stuff / });
`

memcached.get Get the value for the given key.

* key: String, the key
* callback: Function, the callback.

`js
memcached.get('foo', function (err, data) {
console.log(data);
});
`

memcached.gets Get the value and the CAS id.

* key: String, the key
* callback: Function, the callback.

`js
memcached.gets('foo', function (err, data) {
console.log(data.foo);
console.log(data.cas);

// Please note that the data is stored under the name of the given key.
});
`
memcached.getMulti Retrieves a bunch of values from multiple keys.

* keys: Array, all the keys that needs to be fetched
* callback: Function, the callback.

`js
memcached.getMulti(['foo', 'bar'], function (err, data) {
console.log(data.foo);
console.log(data.bar);
});
`

memcached.set Stores a new value in Memcached.

* key: String the name of the key
* value: Mixed Either a buffer, JSON, number or string that you want to store.
* lifetime: Number, how long the data needs to be stored measured in seconds
* callback: Function the callback

`js
memcached.set('foo', 'bar', 10, function (err) { / stuff / });
`

memcached.replace Replaces the value in memcached.

* key: String the name of the key
* value: Mixed Either a buffer, JSON, number or string that you want to store.
* lifetime: Number, how long the data needs to be replaced measured in seconds
* callback: Function the callback

`js
memcached.replace('foo', 'bar', 10, function (err) { / stuff / });
`

memcached.add Add the value, only if it's not in memcached already.

* key: String the name of the key
* value: Mixed Either a buffer, JSON, number or string that you want to store.
* lifetime: Number, how long the data needs to be replaced measured in seconds
* callback: Function the callback

`js
memcached.add('foo', 'bar', 10, function (err) { / stuff / });
`

memcached.cas Add the value, only if it matches the given CAS value.

* key: String the name of the key
* value: Mixed Either a buffer, JSON, number or string that you want to store.
* lifetime: Number, how long the data needs to be replaced measured in seconds
* cas: String the CAS value
* callback: Function the callback

`js
memcached.gets('foo', function (err, data) {
memcached.cas('foo', 'bar', data.cas, 10, function (err) { / stuff / });
});
`

memcached.append Add the given value string to the value of an existing item.

* key: String the name of the key
* value: Mixed Either a buffer, JSON, number or string that you want to store.
* callback: Function the callback

`js
memcached.append('foo', 'bar', function (err) { / stuff / });
`

memcached.prepend Add the given value string to the value of an existing item.

* key: String the name of the key
* value: Mixed Either a buffer, JSON, number or string that you want to store.
* callback: Function the callback

`js
memcached.preprend('foo', 'bar', function (err) { / stuff / });
`

memcached.incr Increment a given key.

* key: String the name of the key
* amount: Number The increment
* callback: Function the callback

`js
memcached.incr('foo', 10, function (err) { / stuff / });
`

memcached.decr Decrement a given key.

* key: String the name of the key
* amount: Number The increment
* callback: Function the callback

`js
memcached.decr('foo', 10, function (err) { / stuff / });
`

memcached.del Remove the key from memcached.

* key: String the name of the key
* callback: Function the callback

`js
memcached.del('foo', function (err) { / stuff / });
`

memcached.version Retrieves the version number of your server.

* callback

memcached.flush Flushes the memcached server.

* callback

memcached.stats Retrieves stats from your memcached server.

* callback

memcached.settings Retrieves your stats settings.

* callback

memcached.slabs Retrieves stats slabs information.

* callback

memcached.items Retrieves stats items information.

* callback

memcached.cachedump Inspect cache, see examples for a detailed explanation.

* server
* slabid
* number
* callback

memcached.end Closes all active memcached connections.

$3

The following methods are intended for private usage

.connect Fetches or generates a connection for the given server. The supplied callback
function will receive a reference to the connection as argument.
If there are issues with the server connection, we are going to respond with cache-miss pattern.

server: String*, The server that needs a connection, the format must be
confirm the server_locations specification.
callback: Function*, The callback function that receives the net.Stre

` js
memcached.connect( '192.168.0.103:11211', function( err, conn ){
if( err ) throw new Error( err );
console.log( conn.server );
});
`

.multi A small wrapper function that makes it easier to query multiple Memcached
servers. It will return the location for each key or the complete list of
servers.

keys: Array* (optional), They keys that needs to be converted to a server.
callback: Function*, The callback function for the data, it will be called
for each key. It will be called with 4 arguments:

1. server: String, The server location.
2. key: String, The key associated with the server, if you didn't specify
keys, this variable will be undefined.
3. index: Number, The current index of the loop
4. total: Number, The total amount server retrieved.

` js
memcached.multi( false, function( server, key, index, totals ){
if( err ) throw new Error( err );

this.connect( server, function( err, conn ){
console.log( "connection ready" )
})
});
`

.command This is the core functionality of the memcached client. All public API's are
routed through this function. It takes care of the argument validations Server
retrieval ( If the server argument isn't specified ). After all data ready a
connection is asked for the private connect method and the command is written
to the Memcached server.

query: Object*, The metaData object, see the Callbacks section for the
specification.
server: String*, The server the to connect. This is only needed when the
metaData object doesn't contain a key property to retrieve the server from.

` js
memcached.command({
key: 'key', callback: function(){ console.dir( arguments ); },

// validate the arguments
validate: [[ 'key', String ], [ 'callback', Function ]],

// used for the query
type: 'delete',
command: 'delete key'
});
`

.connectionIssue A internal function for logging issues with connections. As there can be various
of ways that an error occurs we need solid issue manager to handle all these
cases. For example server could crash or the Memcached server could respond with
SERVER ERROR .

error: String*, The actual error message.
Stream: net.Stream*, A reference to the connection stream where the error
occurred on.
callback: Function* (optional), The callback function of a potential
request, it will be marked as cache miss if it was provided

` js
memcached.connectionIssue( "Server down", connectionReference );
`

Callbacks

Each method requires a callback function. Once this function get executed there
will be 2 variables applied:

* error: A error response if something went wrong while retrieving data from
the Memcached server. Depending on the type of request this will either be an
string or an Array with multiple errors.
* response: The actual result from the Memcached server. If the response is
false or undefined than a cache miss occurred. Cache misses will also
occur when there is an error. So you might want to check on errors first.

When we have a successful response, the context of the callback function will
shift to a metaData object. The metaData object contains all information that we
used to generate the request for the Memcached server. The metaData object
contains the following properties:

* start: Date in milliseconds when the request was received
* execution: Total execution time for the request, including response parsing.
* callback: Reference to the callback function
* type: The type of Memcached command
* command: The compiled command that was send through the sockets
* validate: The properties of metaData object that needs type validation.

And all the arguments you have send to the method, this depends on the method
you have called.

Events

When connection issues occur we send out different notifications using the
EventEmitter protocol. This can be useful for logging, notification and
debugging purposes. Each event will receive details Object containing detailed
information about the issues that occurred.

$3

The details Object contains the various of error messages that caused, the
following 3 will always be present in all error events:

* server: the server where the issue occurred on
* tokens: a array of the parsed server string in [port, hostname] format.
* messages: a array containing all error messages that this server received.
As messages are added to the array using .push(), the first issue will at the
beginning and the latest error at the end of the array.

The following properties depend on the type of event that is send. If we are
still in our retry phase the details will also contain:

* failures: the amount of failures left before we mark the server as dead.
* totalFailures: the total amount of failures that occurred on this server, as when the
server has been reconnected after it's dead the failures will be rest to
defaults and messages will be removed.

If the server is dead these details will be added:

* totalReconnectsAttempted: the total reconnects we have attempted. This is
the success and failure combined.
* totalReconnectsSuccess: the total successful reconnects we have made.
* totalReconnectsFailed: the total failed reconnects we have made.
* totalDownTime: the total down time that was generated. Formula: (
totalReconnectsFailed reconnect_timeout ) + ( totalRetries retry_timeout).

$3

There are 5 different events that the memcached client emits when connection
issues occur.

* issue: a issue occurred on one a server, we are going to attempt a retry next.
* failure: a server has been marked as failure or dead.
* reconnecting: we are going to attempt to reconnect the to the failed server.
* reconnect: successfully reconnected to the memcached server.
* remove: removing the server from our consistent hashing.

Example implementations:

`js
var memcached = new Memcached([ '192.168.0.102:11211', '192.168.0.103:11211' ]);
memcached.on('failure', function( details ){ sys.error( "Server " + details.server + "went down due to: " + details.messages.join( '' ) ) });
memcached.on('reconnecting', function( details ){ sys.debug( "Total downtime caused by server " + details.server + " :" + details.totalDownTime + "ms")});
`

Compatibility


For compatibility with other libmemcached clients they need to have the behavior
ketama_weighted set to true and the hash set to the same as node-memcached's
algorithm.

Due to client dependent type flags it is unlikely that any types other than string will work.

Contributors


* Natalia Angulo _
* Guillermo Menéndez _
* David Fierro `_

(Memcached client: This project wouldn't be possible without the hard work of our amazing
contributors. See the contributors tab in Github for an up to date list of
[contributors] (https://github.com/3rd-Eden/memcached/graphs/contributors).)

Thanks for all your hard work on this project!

License

The driver is released under the MIT license. See the
LICENSE for more information.