My recommended IoT solution reliability checklist: Ensure that the endpoint exposed by the IoT platform is Highly Available to retain connectivity with devices and external applications. The IoT platform endpoint should be highly available to ensure that devices and external applications can always connect to it. Ways to implement: Load balancing: A load balancer distributes incoming traffic across multiple servers, ensuring no single server becomes overloaded. That improves the performance and reliability of the IoT platform.

Tune into the latest episode of my podcast, The Internet of Things Equation, where I sit down with Eric Simone, the CEO of Clearblade. 🎧 In this inspiring conversation, Eric shares his insights on digital transformation, the evolving landscape of IoT, and how Clearblade is making a difference. 📈 Key takeaways: Every Phase Matters ⚛️: Break free from traditional ROI models by showcasing value at each phase of your IoT initiative.

During this conversation with Simon Kemper, CEO of Datacake, we elaborated on designing and building IoT solutions. Simon shared his personal approach to creating trust with customers and an effective marketing strategy. Simon provided a wealth of valuable insights and practical suggestions. Here are some key takeaways from our engaging discussion: Biggest Challenge - Finding Customers: The biggest challenge faced by IoT startups is acquiring customers. There is a great deal of competition for customers, so a clear value proposition and ease of adoption are mandatory characteristics of a successful IoT undertaking.

My take on the state of IoT based on the Eclipse IoT report: IoT has matured and is ready for significant adoption. The importance of Edge Computing is evident to stakeholders. Organizations are ready for larger-scale IoT deployments (>10k assets). Open-source mitigates the vendor-locking risk and provides great flexibility. Connectivity + Security = form the strong foundations for IoT, but… Data Management is more complicated than it seems! Good news: C-level executives are in charge of IoT engagements.

Attention, everyone! Get ready to dive into the fascinating world of the “Internet of Things using AWS Cloud” ebook, now available directly from my website! To celebrate this special occasion, I’m offering an exclusive introductory price of only 15 euros! However, this limited-time offer expires in a week, so don’t miss out on this opportunity to kickstart your AWS IoT journey. After the introductory period, the price will return to its regular rate of 25 euros.

Today, I would like to discuss a particular aspect of designing the MQTT Topic Structure: Should we include an asset’s Physical Location in the MQTT Topic? That is a complex subject, so that I will break it down. Asset Type For consumer electronics like wearables, the location of an asset may be irrelevant or unknown. Even if the use case demands tracking position, we should not record it as a part of the MQTT Topic (devices should send the location in the payload of an MQTT Message stored in a database at the backend).