• How we optimized our build and release pipeline in order to deploy live IoT applications faster
  • IoT Comics - Hackfest Is Served

A good problem to have is growth. Our R&D team recently had the opportunity to work with Microsoft developers on reducing the overhead involved in on-boarding new clients, and introducing increased scalability.

Micro-services break up a large project into smaller services organized around business functions. These smaller services can be enhanced and extended individually without impacting the full application. They can be optimized and scaled independently.

Each “IoT event” should use the micro-services it needs, in order to optimize the architecture per event.

Due to accelerating growth, we needed a way to deploy hundreds of data gateways, a micro-service that standardizes the data structure of any sensor or system, so that the IoT application can run business logic, rules, alerts and analytics on data from different sources.

The micro-services needed to get to our Azure Managed Kubernetes – AKS cluster. We worked with the Microsoft Commercial Software Engineering team (CSE) to find a solution that would maximize customer flexibility and scalability.

Microsoft wrote a full post on how to use Helm and Expose as a service. They provide diagrams and code examples on building a K8S Http API for Helm and serve micro-services using a single IP.  Many companies are looking to serve multiple micro-services in an automated manner. This post by Microsoft and Axonize will explain how this is done, by giving you an in-depth look into the architecture that makes this a possibility. Check out the full post here: “How to Build A K8S Http API For Helm, and Serve Micro-services Using A Single IP”.