Azure IoT Gateway SDK has evolved into Azure IoT Edge on May 10, 2017. To learn more click here.

Back in November, we announced the general availability of the Azure IoT Gateway SDK. We’ve already heard from a number of customers who are leveraging the open source Gateway SDK to connect their legacy devices or run analytics at the edge of their network. It’s great to see quick adoption! With the Gateway SDK’s modular architecture, developers can also program their own custom modules to perform specific actions. Thanks to its flexible design, you can create these modules in your preferred language – Node.js, Java, C#, or C.

We want to further simplify the experience of getting started with writing modules for the Gateway SDK. Today, we are announcing availability of packages to streamline the developer experience, enabling you to get started in minutes!

What packages are available?

1. NPM
   • azure-iot-gateway: With this you will be able to run the Gateway sample app and start writing Node.js modules. This package contains the Gateway runtime core and auto-installs the module dependencies’ packages for Linux or Windows.
   • generator-az-iot-gw-module: This provides Gateway module project scaffolding with Yeoman.
2. Maven
   • com.microsoft.azure.gateway/gateway-module-base: With this you will be able to run the Gateway sample app and start writing Java modules. You only need this package and its dependencies to run the Gateway app locally, but you do not need to include them when you publish your gateway. This package contains the Gateway runtime core and links to the module dependencies’ packages for Linux or Windows.
   • com.microsoft.azure.gateway/gateway-java-binding: This package contains the Java binding or interface. This package is required for both runtime and publishing.
3. NuGet
   • Microsoft.Azure.Devices.Gateway: This package contains the Gateway runtime core.
   • Microsoft.Azure.IoT.Gateway.Module: This package includes the module dependencies required to run the Gateway sample app and write .NET Framework modules on Windows.

What does this mean for you?

The primary benefit of these packages is time saved. They significantly reduce the number of steps required to start writing a module. You no longer have to clone and build the whole Gateway project. In addition, the packages include all the dependencies for you to mix modules written in different languages.

What’s next?

.NET Core NuGet packages are coming soon. We are looking for further ways to improve the Gateway SDK developer experience. For more information on getting started with these packages, check out our GitHub sample apps.

We’re delighted to see developers contributing their modules to the Gateway SDK community. Our team looks forward to seeing further activity in this area and learning more about your gateway scenarios. So take the new packages for a spin, and let us know what you think!