Announcing Azure Mobile Apps Node.js Server SDK v2.1.0

Posted on April 19, 2016

Sr. Program Manager, Azure App Service Mobile Apps

When we released the v2.0.0 GA release of the Azure Mobile Apps Node.js Server SDK, we had some unfinished business to deal with. Most notable among the customer asks was the ability to run a local development edition of the server without needing a SQL Server. The v2.1.0 release of the Server SDK adds support for SQLite on the server. This provides a new data store that can be used for a number of important scenarios:

Local development

The SQLite data provider brings a greatly simplified local development experience to all platforms, including OS X and Linux. SQLite runs on all node.js versions and platforms, requires no external database and can run entirely in memory.

The data provider works without any configuration and is configured to be the default provider, enabling zero configuration local development that just works and can be switched over to using a SQL Azure instance without zero code changes between the local development environment and Azure production environment.

Unit/integration test suite

One of the main items is the ability to test your service locally using unit and integration tests based on Mocha, Jasmine or another test framework. The main problem here is that tests can leave your database in a bad state, causing failures that are due to the SQL state rather than your database. Using the SQLite database enables the tests to be run with an in-memory provider that is refreshed with a known good state prior to every single test run. This allows you to automate the testing through a variety of continuous integration solutions.

Support for AAD groups

Azure Mobile Apps supports authentication via Facebook, Twitter, Google+, Microsoft and Azure Active Directory. This latter mechanism provides support for enterprise mobile applications. We now support a full decoding of the AAD claims, which includes AAD Group membership. If you have configured AAD to provide groups as a claim, these will be available via the getIdentity()call.

Continual improvements to documentation

In addition to the above, we've made some more improvements to the samples and the API reference. We're committed to continually improving our samples and documentation, so if you want to see something in this area, let us know.

You can find the complete list of changes here.  All of our SDKs are open source and we welcome contributions.

Contacting the team

The Azure Mobile Apps team can be contacted through one of the following mechanisms: