fast-azure-storage

Fast Azure Storage Client for Node.js

This library implements a low-level and highly optimized interface to Azure Storage Services. Existing node libraries for Azure suffers of excessive complexity, dependencies, being slow and not managing connection correctly.

At this point this library implement most of the APIs for queue and table storage. Pull request with additional feature additions will generally be accepted, as long as patches don't compromise efficiency.

For full documentation see reference documentation or extensive comments in the sources.

Common Client Options

Both Queue and Table takes a range of common configuration options.

Authentication Options

The following example illustrates how to create clients using shared key authentication.

// Load fast-azure-storage client
var azure = require('fast-azure-storage');

// Common options using shared key authentication
var options = {
  accountId:          '...',
  accessKey:          '...'
};

// Create queue and table clients
var queue = new azure.Queue(options);
var table = new azure.Table(options);

It's also possible to configure clients with Shared-Access-Signatures as illustrated in the following example.

// Common options using shared-access-signatures
var options = {
  accountId:          '...',
  sas:                sas   // sas in querystring form: "se=...&sp=...&sig=..."
};

In fact it's possible to provide a function that will be used to refresh the Shared-Access-Signature when it's close to expire:

// Common options using shared-access-signatures
var options = {
  accountId:          '...',
  sas:                function() {
    return new Promise(/* fetch SAS from somewhere */);
  },
  // Time to SAS expiration before refreshing the SAS
  minSASAuthExpiry:   15 * 60 * 1000
};

Custom HTTPS Agent Configuration

The fast-azure-storage library comes with a custom https.Agent implementation, optimized for Azure Storage service to reduce latency and avoid errors. By default both Table and Queue clients will use a global instance of this custom agent configured to allow 100 connections per host.

You may override this behavior by supplying your own agent as follows.

// Common options for HTTPS agent configuration
var options = {
  agent:      new azure.Agent({...}),
};

Please, read the Built-in Azure HTTPS Agent section for details on why this custom https.Agent is necessary. Notice that while it's strongly recommended to use the HTTPS agent that ships with this library as oppose the default https.Agent implementation, it's perfectly sane to tune the options of the HTTPS agent that ships with this library, and even create multiple instances of it if you feel that is necessary.

Azure Table Storage Client

The Azure Storage Table client aims at interfacing Azure Table Storage without abstracting away the storage format and type information stored with each entity. It assumes that opinionated abstractions will do type conversions as necessary.

Simple example of table and entity creation.

// Load fast-azure-storage client
var azure = require('fast-azure-storage');

var table = new azure.Table({
  accountId:    '...',
  accessKey:    '...'
});

// Create table and insert entity
table.createTable('mytable').then(function() {
  return table.insertEntity('mytable', {
    PartitionKey:         '...',
    RowKey:               '...',
    'count':              42,
    '[e-mail]':   'Edm.Int64',
    'buffer':             new Buffer(...).toString('base64'),
    '[e-mail]':  'Edm.Binary'
  });
});

Table API Reference

See also reference documentation.

• Table(options)
• Table#queryTables(options)
• Table#createTable(name)
• Table#deleteTable(name)
• Table#getEntity(table, partitionKey, rowKey, options)
• Table#queryEntities(table, options)
• Table#insertEntity(table, entity)
• Table#updateEntity(table, entity, options)
• Table#deleteEntity(table, partitionKey, rowKey, options)
• Table#sas(table, options)
• Table.filter(expression)

Azure Queue Storage Client

The Azure Storage Queue client aims at interfacing Azure Queue Storage and handling all the XML parsing using libxmljs if available, if libxmljs isn't available it'll fall-back to use pixl-xml which is a pure Javascript, but also a tiny bit slower.

Simple example of queue and message creation.

// Load fast-azure-storage client
var azure = require('fast-azure-storage');

var queue = new azure.Queue({
  accountId:    '...',
  accessKey:    '...'
});

// Create queue and insert message
queue.createQueue('myqueue').then(function() {
  return queue.putMessage('myqueue', 'my-message', {
    visibilityTimeout:  10,     // Visible after 10 seconds
    messageTTL:         60 * 60 // Expires after 1 hour
  });
});

Queue API Reference

See also reference documentation.

• Queue(options)
• Queue#listQueues(options)
• Queue#createQueue(name, metadata)
• Queue#deleteQueue(name)
• Queue#getMetadata(queue)
• Queue#setMetadata(queue, metadata)
• Queue#putMessage(queue, text, options)
• Queue#peekMessages(queue, options)
• Queue#getMessages(queue, options)
• Queue#deleteMessage(queue, messageId, popReceipt)
• Queue#clearMessages(queue)
• Queue#updateMessage(queue, text, messageId, popReceipt, options)
• Queue#sas(queue, options)