The Ultimate IoT Backend using Node.js, Serverless and Kubernetes

In this post, we’ll cover the components of an IoT backend using Node.js, FaaS (functions-as-a-service or serverless) and Kubernetes to sustainably build a backend to your IoT applications. We’ll provide new concepts, as well as helpful tips to get you off to a great start.

What is an IoT Backend? {.p2}

There are a few primary components to constructing the backend of an IoT application.

  • Data StorageYou need the right tools to manage your machine data can make the difference between success and failure.
  • ProtocolsDevices or “things” communicate through more compact and efficient the payloads We’re talking about protocol support just as MQTT and CoAP in addition to standard JSON over REST.
  • AnalyticsIt’s not enough to just collect and store data. In order to truly have an impact on your growth trajectory, you need analytics to provide valuable insights.
  • ServicesNext, you need the appropriate services to be able to execute on those insights.

So, all of these components take expertise to understand. When it comes to stitching them altogether, it can be difficult for enterprise executives and developers to understand where to start.

Where do Node.js, Serverless and Kubernetes fit in? {.p2}

As you begin to think about how to design your backend, you need to consider different aspects of your API Strategy. Specifically, what languages can you use (such a Node.js) that will help you hire quickly or maintain a flexible and productive development environment. For developers, choosing a Runtime may not seem important, but Docker and Kubernetes make your Runtime portable because every cloud provider supports containers.  In addition, Serverless provides a layer of ease of use and productivity.

So even if you’re just focused on Microservices integration and composition, you can still achieve seamless API and Microservices development.

API Growth Strategies Start With API Management

As you already know, API Management is a key growth strategy for Enterprise companies and developers alike.

In our example, we have used Node.js, Docker and Serverless runtime as a powerful combination within the LunchBadger platform. Even though we are using this to build an Backend for our IoT application, it works for a broad spectrum of use cases.

If you have already been on the LunchBadger platform, you’ll notice that there’s a brand new box in the GUI. (We’ll have more on that in the upcoming weeks!)

Express Gateway as the API Gateway Solution

An API Gateway Solution is just one last piece to the puzzle. By now, you will have heard of our open source project, Express Gateway.  As cosponsors of Express Gateway, we’re partnering with Joyent and the Node.js developer community to provide an open source API Gateway built entirely on Express.js.

Together, we provide a simple, flexible and community driven open source tool that can be used anywhere by anyone.

The API Gateway is at the heart of Microservices which means it will continue to play an important part in your IoT Backend. We are keeping Express Gateway open source because we believe that developers deserve next generation tooling. When you pair this project with an infrastructure platform like LunchBadger which supports the management and composition of your microservices, you can get started in minutes – not hours or days.

Think Function As A Service

If you have never heard of this term before, get with the program!

Function as a service (FaaS) describes a category of cloud computing services which are a platform. This platform allows customers to run, develop and manage application functionalities without having to build or maintain the infrastructure.

Instead of having to maintain all of your own infrastructure, you can leverage a platform to do it for you? Seems pretty simple. However; it’s very powerful and can help you add some velocity to your development cycles.

Key Takeaways

Express Gateway gives you API gateway capabilities while LunchBadger gives you composition and aggregation/mashup for rolling up fine grain microservices into engagement level APIs.

In the next week, we’ll share a live demo on our latest concepts.

  • How to pull together Serverless, Docker/Kubernetes (Runtime) and an open source API gateway into an easy to use platform
  • How to conserve resources at the Enterprise level to maximize productivity
  • and more ideas on how to pilot this within your company.

If you’ve been looking for a deep dive into LunchBadger’s capabilities and ease of use or just protips on how to execute your API Strategy – stay tuned for more!

Moving On

Next week, we’re headed to the Samsung Developer’s Conference to make some noise with the co-sponsor of Express Gateway, Joyent. Building IoT applications is hard enough, building a sustainable backend infrastructure shouldn’t be.

So we’ve chosen the Samsung Developer’s conference as a way to make this important aspect of your tech stack easier, more flexible and with a little love from open source tools like Express Gateway, an open source API gateway built entirely on Express.js.

Additionally, if you’re interested in more of these topics, join the live discussion on twitter (@lunchbadger) or (@express_gateway).

If you have questions about Express Gateway or want to get more involved in our community, please consider joining our Gitter. We’ve been working hard to create an open and transparent environment where you can get your questions answered and meet other devs interested in open source.