azurite

What is azurite?

Azurite is an open-source Azure Storage API compatible server (emulator). It provides a local environment for testing and development of applications that use Azure Storage services, including Blob, Queue, and Table storage.

What are azurite's main functionalities?

Blob Storage

This code snippet demonstrates how to start the Azurite Blob service on port 10000. Blob storage is used for storing large amounts of unstructured data such as text or binary data.

const azurite = require('azurite');
azurite().blob().listen(10000, () => {
  console.log('Azurite Blob service is running on port 10000');
});

Queue Storage

This code snippet demonstrates how to start the Azurite Queue service on port 10001. Queue storage is used for storing large numbers of messages that can be accessed from anywhere via authenticated calls.

const azurite = require('azurite');
azurite().queue().listen(10001, () => {
  console.log('Azurite Queue service is running on port 10001');
});

Table Storage

This code snippet demonstrates how to start the Azurite Table service on port 10002. Table storage is used for storing structured NoSQL data.

const azurite = require('azurite');
azurite().table().listen(10002, () => {
  console.log('Azurite Table service is running on port 10002');
});

Other packages similar to azurite

localstack

LocalStack is a fully functional local AWS cloud stack. It provides a local testing environment for AWS services, including S3, DynamoDB, and SQS. Unlike Azurite, which focuses on Azure Storage services, LocalStack emulates a wide range of AWS services.

minio

MinIO is a high-performance, S3-compatible object storage system. It is designed to be used for large-scale data infrastructure. While Azurite emulates Azure Blob storage, MinIO provides an alternative for S3-compatible object storage.

fake-s3

Fake S3 is a lightweight server that emulates the S3 API. It is useful for testing S3 interactions locally. Unlike Azurite, which emulates Azure Storage services, Fake S3 focuses solely on the S3 API.

README

Azurite

A lightweight server clone of Azure Blob Storage that simulates most of the commands supported by it with minimal dependencies.

Installation and Usage

NPM

In order to run Azurite you need Node.js >= 6.0 installed on your system. Azurite works cross-platform on Windows, Linux, and OS X.

After installation you can install Azurite simply with npm which is Node.js package management tool and which is included with every Node.js installation.

$ npm install -g azurite

Then simply start it with the following command:

$ azurite -l path/to/localfolder

This tells Azurite to store all data in a particular directory. If the -l option is ommitted it will use the current working directory. This also will start both blob storage and queue storage emulation in two different processes. You can also selectively start the different storage emulators.

For Blob Storage Emulator only:

$ azurite-blob -l path/to/localfolder

For Queue Storage Emulator only:

$ azurite-queue

Nuget

Azurite is also available as Nuget package at https://www.nuget.org/packages/Azurite/. You can install it via the Package Manager Console with the following command:

PM> Install-Package Azurite

This will install Azurite to your current project and also immediately start it in a dedicated console window. Note that you do not need to install Node.js since Azurite is packaged into a single self-contained executable, thanks to pkg.

Docker image

Pulling from Docker Hub

Every release of Azurite starting with version 0.9.7 is available at Docker Hub and ready to be pulled with:

$ docker pull arafato/azurite

Please note that the latest tag will always refer to the latest release.

Build the Docker image

To build the Docker image yourself, execute the following:

$ docker build -t arafato/azurite .

Run the Docker image

To run the Docker image, execute the following command:

$ docker run -d -t -p 10000:10000 -p 10001:10001 -v /path/to/folder:/opt/azurite/folder arafato/azurite

Configure the executable when running the container

By default, the container starts all services available (currently blob and queue). Using the environment variable executable, specific executables can be specifed:

• blob Start the Blob Storage Emulator only
• queue Start the Azure Queue Storage Emulator only

Usage example:

$ docker run -e executable=blob -d -t -p 10000:10000 -v /path/to/folder:/opt/azurite/folder arafato/azurite

Contributions

What do I need to know to help?

If you are interested in making a code contribution and would like to learn more about the technologies that we use, check out the list below.

• Azurite runs on Node.js. If you never worked with this technology before make sure to get yourself familiar with it. There are many good tutorials out there along with a comprehensive API documentation that will get you up to speed quickly! We are currently coding against Node.js v6.10.x LTS
• Azurite exposes its REST-based API via Express.js which is a "fast, unopinionated, minimalist web framework for Node.js.
• Azurite uses LokiJS which is an in-memory data store with persistence. It serves as our central database to store metadata (names, properties, leases, etc.) about all objects put into Azurite.
• Azurite makes heavy use of Bluebird which is a fully featured promises library with unmatched performance.

What TODOs are there?

The current status of Azurite's support of the Official Blob Storage REST API Specification is listed in below section API Support. Features that are still unimplemented are marked with [TODO]. Features that are currently being worked on are marked with [IN-PROGRESS].

Current bugs that need to be fixed are listed at our issues site on Github and tagged with a red label bug.

How do I make a contribution?

Never made an open source contribution before? Wondering how contributions work in Azurite? Here's a quick rundown!

1. Find an issue that you are interested in addressing or a feature that you would like to add.

2. Fork the Azurite repository to your local GitHub organization. This means that you will have a copy of the repository under your-GitHub-username/azurite.

3. Clone the repository to your local machine using git clone https://github.com/github-username/azurite.git.

4. Create a new branch for your fix using git checkout -b branch-name-here. Make the appropriate changes for the issue you are trying to address or the feature that you want to add.

5. Use git add insert-paths-of-changed-files-here to add the file contents of the changed files to the "snapshot" git uses to manage the state of the project, also known as the index.

6. Use git commit -m "Insert a short message of the changes made here" to store the contents of the index with a descriptive message.

7. Push the changes to the remote repository using git push origin branch-name-here.

8. Submit a pull request to the upstream repository. Title the pull request with a short description of the changes made and the issue or bug number associated with your change. For example, you can title an issue like so "Added more log outputting to resolve #4352". In the description of the pull request, explain the changes that you made, any issues you think exist with the pull request you made, and any questions you have for the maintainer. It's OK if your pull request is not perfect (no pull request is), the reviewer will be able to help you fix any problems and improve it!

9. Wait for the pull request to be reviewed by a maintainer. Make changes to the pull request if the reviewing maintainer recommends them.

10. Celebrate your success after your pull request is merged!

Where can I go for help?

If you need help, you can ask questions directly at our issues site on Github.

API Support

Currently, Azurite only supports the Blob Storage APIs, and the Queue Storage API. Support for Azure Storage Files and Azure Storage Tables is planned (see https://github.com/arafato/azurite/issues/114 for details), but currently not available.

The Standard Emulator Connection String is the same as required by Microsoft's Official Storage Emulator:

BlobEndpoint=http://127.0.0.1:10000/devstoreaccount1;

QueueEndpoint=http://127.0.0.1:10001/devstoreaccount1;

Blob Storage - API Implementation Status

All DONE except:

• Account SAS Support [TODO]
  See https://docs.microsoft.com/en-us/rest/api/storageservices/constructing-an-account-sas for specification

• Set Blob Service Properties [TODO]
  Sets the properties of the Blob service, including logging and metrics settings, and the default service version.

• Get Blob Service Properties [TODO] Gets the properties of the Blob service, including logging and metrics settings, and the default service version.

• Preflight Blob Request [TODO]
  Queries the Cross-Origin Resource Sharing (CORS) rules for the Blob service prior to sending the actual request.

• Get Blob Service Stats [TODO]
  Retrieves statistics related to replication for the Blob service. This operation is only available on the secondary location endpoint when read-access geo-redundant replication is enabled for the storage account.

• Set Blob Tier [TODO] The Set Blob Tier operation sets the tier on a blob.

Queue Storage - API Implementation Status

All DONE except:

• Set Queue ACL (https://github.com/arafato/azurite/issues/100) [In-PROGRESS]
• Get Queue ACL (https://github.com/arafato/azurite/issues/99) [IN-PROGRESS]