Telemetry buffering on IoT gateways during connectivity loss
A practical matrix for selecting what an IoT gateway stores, evicts, and retransmits after a connection loss, considering MQTT 5.0 and Sparkplug B standards.

Co-founder, Softline and Intecracy Group
IT entrepreneur and manager with over 30 years of experience; focuses on IT strategy, investment, cybersecurity, digital transformation, and process automation.
In the AZIOT knowledge base, the expert provides strategic commentary on published articles: investment, governance, security, and architecture angles for infrastructure decisions.
A practical matrix for selecting what an IoT gateway stores, evicts, and retransmits after a connection loss, considering MQTT 5.0 and Sparkplug B standards.
Choosing the optimal architecture for cryptographic key management on resource-constrained IoT devices is a critical decision impacting security, cost, and operational efficiency. It necessitates balancing hardware protection with device limitations such as power consumption and memory.
Choosing an architectural approach to protect critical infrastructure IoT sensors from false data injection is a strategic decision that requires balancing data reliability, implementation complexity, and computational resources. This article examines architectural patterns for verifying data integrity at various system levels.
Implementing a multi-tenant IoT platform demands careful selection of architectural patterns to ensure stringent data and access isolation, balancing cost, scalability, and security. This is critical for integrating devices, sensors, and telemetry.
For IIoT architects and operations engineers, selecting the optimal MQTT 5.0 Quality of Service (QoS) level and complementary architectural patterns is key to guaranteeing critical telemetry data delivery in unstable network environments.
Selecting the right architectural approach to ensure the immutability and auditability of IoT data, from sensor to storage, is critical for meeting regulatory requirements. This balances performance, storage costs, and the level of trust in data integrity within regulated environments.
Improper decommissioning of IoT devices poses significant risks of data breaches and their transformation into 'zombie devices'. Implementing standardized mechanisms for certificate revocation, secure data sanitization, and network isolation is critical to minimizing these threats.
Modernizing legacy Operational Technology (OT) demands a strategic decision: whether to integrate an IoT overlay to extend functionality or to completely replace systems with modern IoT-oriented solutions. This dilemma impacts investments, risks, and the long-term flexibility of infrastructure.
In multi-tenant buildings and industrial zones, clearly defining IoT data ownership and access rules is critical to prevent operational disruptions and ensure regulatory compliance.
Unifying legacy industrial and building protocols like Modbus, BACnet, and KNX into a single IoT platform is crucial for infrastructure modernization. This article explores architectural trade-offs and strategies for successful integration in complex B2B environments.
For utility infrastructure architects, it's critical to understand that simple radio coverage doesn't guarantee LoRaWAN effectiveness. Duty cycle, collisions, and downlink budget must be accounted for to ensure scalable and reliable network operation.
Implementing Matter in multi-dwelling units necessitates clear demarcation of device ownership and management. This approach helps prevent conflicts and ensures system security and scalability.