Operations | Monitoring | ITSM | DevOps | Cloud

(This blog post is part of a 5 part series, titled “How to launch IoT devices”. It will cover the key choices and concerns when turning bright IoT ideas into a product in the market. Sign up to the webinar on how to launch IoT devices to get the full story, all in one place.) First part: Why does IoT take so long? Second part: Select the right hardware and foundations Third part: IoT devices and infrastructure

In the first part of this blog article, I introduced key concepts surrounding data ingestion for the industrial Internet of Things, the role and importance of metrics and self-services capabilities for shop floor personnel. So let's see how this looks in practice and how the knowledge of a process or control engineer can be turned into action.

Industry 4.0 technology is transforming industry all over the world. Digital innovations such as data, virtual reality, automation, and robotics are all helping brands create products and services and deliver them to customers in better and more efficient ways than ever before. One of the most useful elements of Industry 4.0 technology comes from the Internet of Things.

Single-node deployments of Kubernetes are more common than what one would expect. In some scenarios, single-node clusters make much more sense. For development purposes or testing, there’s no need to deploy a full-blown production-grade cluster. Single-node deployments are also handy for appliances and IoT applications since they have a much smaller footprint. Enter MicroK8s, a tool by Canonical that enables you to easily deploy a lightweight single-node cluster in your local environment.

The Internet of Things (IoT) revolution has set the beginning of a new age of data transfer. Each day, a massive number of new devices get added to all kinds of network infrastructures, transferring gargantuan amounts of data back and forth. In the next decade, we expect the number of IoTs to grow to a staggering 80 billion connected devices – practically outnumbering the human population tenfold.

By next year the number of connected devices will exceed 20 billion. The vast majority of these devices run on Arm architecture, increasingly at the infrastructure edge. With this growth in mind, the need for an agile, Arm-based development methodology has become increasingly urgent. Arm Neoverse provides the required IP for building the next gen of edge to cloud infrastructure to support the data explosion we are seeing, primarily caused by IoT.