Modern solutions utilize distributed infrastructure to deliver business value. Manual management of those assets is error-prone, time-consuming, and does not scale. Fortunately, we often leverage a virtual infrastructure offered by the cloud providers. One of the benefits of a cloud is that we can describe it using code. That approach is called Infrastructure as Code (IaC). ​ ​What benefits does IaC offer?​ ​ IaC enables using agile software development methodology to describe and manage infrastructure.

This diagram represents the steps required to transform a self-storage business into a global trusted partner. IoT provides tools for that change, but the transformation requires more than simply installing shiny devices. When we transform an enterprise, we change how it operates and offers services. That is a mental shift rather than a technical undertaking. Static version of the above diagram: link You can find the recording of my live stream on this topic on YouTube:

I’ve got a new IoT companion :) Unfortunately, our cooperation is not as smooth as I had hoped, but we are slowly getting along. That brings me to the following question: In what cases are simulating devices good enough, and when must we use real hardware? I often simulate IoT devices because they are managed using software that enables: Fast initial setup. Efficient prototyping. Load testing of any number of units.

Summary A kind reminder: the Internet of Things is not the root cause of every cybersecurity threat. More importantly, we can leverage the IoT capabilities to counter most of the security challenges! Reasoning The Internet of Things is commonly perceived as the root cause of every cybersecurity threat. I disagree with that approach. The IoT system is as secure as we (architects and developers) build it. What is true is the following:

Overview Before defining the profitable business model for the IoT Startup, you need to estimate the initial investment and operational costs. The initial investment covers the design and implementation of the following: Connectivity and IoT Backend infrastructure. End-user Software and Backend. Hardware and Firmware. Security. Those are substantial costs, but what makes IoT initiatives fail are the operational expenses, including: Connectivity. Cloud resources. End-user support. Consumption model. After estimating those costs, we are ready to define the business model.

Definition: A framework is an essential supporting structure that allows building things upon it. Whenever I help customers design and build an Internet of Things solution, I typically recommend starting with the IoT Framework. Beginning the solution development without defining the framework introduces significant risk. The created functionality delivers the expected business outcomes but (often) does not support adding new capabilities. As a result, the code base becomes challenging to manage, hindering future extensions and error-prone.