Download the PDF

Introduction

Gateways play a critical role in Commercial IoT applications. They manage end devices in a complex environment, collect and analyze data, provide local command and control, secure edge infrastructure, and communicate processed and/or aggregated data to the cloud. Determining your requirements for the gateway for your specific IoT use case is an important first step in designing an IoT solution. As prototyping an IoT gateway solution can help, I’m often asked about the best approach. And, more specifically, if Raspberry Pi or another solution is the best starting point. The answer depends in part on your particular needs when it comes to project timing, level of required support, hardware adaptability, production scale, security, power, connectivity, exterior appearance, and your business case.

As a result, in this article I’ll walk through two common IoT gateway prototyping approaches: Raspberry Pi and commercial-grade production gateways. Both with the common goal of scalable, cost-effective mass production in mind.

Raspberry Pi

Project Timing

If you need to get started quickly Raspberry Pi is certainly a viable option, as they can be purchased readily on hundreds of websites. With hardware in hand you can get started right away. Unfortunately, the Pi does not come with an operating system, so you will need to spend some time choosing the right one and installing it on your one or more devices.

You may need to spend additional time once the OS is up and running determining add-ons required to make the Pi into a full featured IoT gateway.

Power
Power is a critical consideration for your IoT gateway, especially as many commercial buildings today use Power over Ethernet (PoE). Installing Ethernet cabling, considered a “low voltage” installation, significantly simplifies installation and reduces cost, as PoE is less expensive than wiring in an outlet. Raspberry Pi does not offer PoE as an option, however this is mitigated by adding on a PoE adapter.

Connectivity
The Raspberry Pi 3 has both Wi-Fi and Bluetooth built in. This can pose an issue, though, if you try to stream too much data, as the two radios will compete for air time. For example, if your project will scan Bluetooth Low Energy (BLE) for nearby devices advertising sensor data or location information, your system will effectively be deaf every time the Wi-Fi radio sends a packet to the cloud.
Conversely, if your use case requires cellular connectivity, using Raspberry Pi means you’ll need to plug in a USB modem. You will also require a daughter card if you need BLE 5.0, Thread, ZigBee or other proprietary mesh protocol.

Support
Raspberry Pi has a great online community. It is very active and many of the common pitfalls of setting the device up as an IoT gateway have already been experienced and overcome by other users. This being true, you will still need to do all the investigation and educate yourself very thoroughly to be successful. In the end you will need to be your own best support for the product throughout prototyping and even through its complete life cycle as your implementation will be unique to you. Further, if you get beyond prototyping and plan to deploy in a Commercial IoT application at scale you will need to build out your own 24/7 support system.

Hardware Adaptability and Optimization
If you are looking for the most hardware flexibility and adaptability, then the Raspberry Pi is certainly the way to go. There are many, many ways to add functionality and capacity in all of the components. The challenge comes when you look to optimize the hardware for cost, ability, and efficiency at scale after you are done prototyping. Often times you will end up paying more at scale because your OS takes up a lot of space and so you need extra storage in each gateway. Or your Bluetooth antenna does not have good range, so you’ll need twice as many gateways as you expected to cover the area required in your solution. Finally, in many commercial environments you will need your final hardware configuration to be certified before it can be used in production, which can be time consuming process.

Security
This is one area where the Pi will not compare very well. By default, security at each level (hardware, OS, network, application, etc.) will have to be implemented from scratch by you. For Commercial IoT use cases, you will need to secure the Pi in many ways to thwart the vulnerabilities inherent in having a connected computing device in a physically unsecured environment like a hotel room, restroom, or warehouse. Further, assuming you choose one of the common operations systems you will also need a way to keep it up-to-date, as new versions of the OS are released to protect against CVEs that are discovered. Thought this effort will not be too bad in prototyping it will be particularly challenging with hundreds or thousands of these gateways in a production environment.

Appearance
Can you imagine the Raspberry Pi with its open plugs, connectors and motherboard at your local restaurant or retailer? Luckily, the popularity of the Raspberry means that you can easily find enclosures (though most are intended for hobbyists). In my experience, companies want a sleek IoT gateway enclosure with design elements for cable management, and often wall or ceiling mount options for installation.

Cost and TCO
The cost analysis of using a Raspberry Pi is similar to the cost analysis of almost any DIY solution, the acquisition cost of the base product is very affordable and looks appealing. However, once you have purchased all of the additional parts (extra antennas, cellular modem, enclosure, etc.) to make it into a fully featured, deployment-ready IoT gateway the cost is significantly more. Then there is a total cost of ownership, after the prototyping phase, based on the costs of building out a deployment, management, and security platform so that the solution can really function at scale. Finally, there are costs related to the increased risk associated with a first-of-a-kind product, along with building out an ongoing support department, and possible lost opportunity due to a longer time-to-market.

Production-Ready Gateway

Next let’s assess production-ready commercial IoT gateways against these elements.

Project Timing
The actual purchase and acquisition of the IoT gateway will take longer with a commercial solution than with the Raspberry Pi. Since these commercial solutions are production-ready you will more than likely want to do a feature and cost comparison and possibly even a POC on several different models and/or services. However, once you decide on a solution, getting the solution up and running will happen 5-6 times faster with the commercial solution than with the Pi. In the end you will get through POC and prototyping, and move on to production, significantly faster than on a Pi, and you should also be able to build on the same platform through each development stage shortening time to market.

Stay up-to-date with the Rigado Newsletter

Subscribe