Building A Serverless IoT Architecture

Building A Serverless IoT Architecture
Facebook may have decided that you shouldn’t see the news, but we think you deserve to be in the know with Lifehacker Australia’s content. To sign up for our daily newsletter covering the latest news, hacks and reviews, head HERE. For a running feed of all our stories, follow us on Twitter HERE. Or you can bookmark the Lifehacker Australia homepage to visit whenever you need a fix.

Few things instill more fear when I think of network architecture and security than thousands of tiny devices collecting and sending data across a network. The Internet of Things is a rising tide that will mean there will be between five and ten devices connected to the Internet for every many, woman and child on the planet before the decade is out. A recent experiment sought to discover whether a serverless architecture was worth exploring when deploying an IoT solution.

The experiment, summarised at IoT for All and covered in more detail in a white paper [PDF] describes how to create a simulated environment using various AWS services.

The experiment simulated 10,000 devices reporting small volumes of data every 15 minutes. Based on the services they deployed, this ran up a cost of about US$160 per month.

Although this was an experiment, it’s a good insight into one way to manage IoT devices. Given many devices come with limited management interfaces and poor, if any, security, it’s important to create an IoT environment that supports those needs.

Are you deploying a large-scale IoT project? How are you architecting it? It would be great to hear how other IT professionals are solving these challenges.


  • What are your thoughts on a serverless IoT architecture? How would this affect the connectivity between each and every person on this planet?

Comments are closed.

Log in to comment on this story!