
Sign up to save your podcasts
Or


Derek Tuando, IoT specialist and creator of LoRaDB, talks about why traditional databases often fall short when applied to real-world LoRaWAN deployments, and what changes when data systems are designed with devices—not tables or tags—as the primary organizing principle.
Derek explains what an IoT database actually is, drawing clear distinctions between general-purpose databases, time-series tools, and systems purpose-built for LoRaWAN workloads. He outlines the practical challenges that emerge as projects grow beyond early pilots, including query complexity, usability issues, and the friction teams face when stitching together multiple tools just to visualize and understand device data.
The conversation dives into the core idea behind LoRaDB’s device-first data model, where all data is organized around a device’s identity rather than abstract measurements. Derek walks through how this approach simplifies querying, speeds up exploration, and makes LoRaWAN data more intuitive to work with—especially for small teams, hobbyists, and lean organizations managing thousands to tens of thousands of devices.
Derek also discusses where LoRaDB fits today, including its strengths in ease of setup, open-source accessibility, and built-in visualization, as well as its current limitations around high availability and large-scale enterprise deployments. He shares how the project is being used in production, why it’s designed to complement existing LoRaWAN stacks like ChirpStack, and how future improvements are focused on lowering the barrier for new users rather than chasing complexity.
This episode offers a grounded look at the data layer of LoRaWAN systems, with practical insights for builders, operators, and businesses deciding how to store, query, and actually use the data their devices generate.
Links
Derek on LinkedIn
LoRaDB on Github
By MeteoScientificDerek Tuando, IoT specialist and creator of LoRaDB, talks about why traditional databases often fall short when applied to real-world LoRaWAN deployments, and what changes when data systems are designed with devices—not tables or tags—as the primary organizing principle.
Derek explains what an IoT database actually is, drawing clear distinctions between general-purpose databases, time-series tools, and systems purpose-built for LoRaWAN workloads. He outlines the practical challenges that emerge as projects grow beyond early pilots, including query complexity, usability issues, and the friction teams face when stitching together multiple tools just to visualize and understand device data.
The conversation dives into the core idea behind LoRaDB’s device-first data model, where all data is organized around a device’s identity rather than abstract measurements. Derek walks through how this approach simplifies querying, speeds up exploration, and makes LoRaWAN data more intuitive to work with—especially for small teams, hobbyists, and lean organizations managing thousands to tens of thousands of devices.
Derek also discusses where LoRaDB fits today, including its strengths in ease of setup, open-source accessibility, and built-in visualization, as well as its current limitations around high availability and large-scale enterprise deployments. He shares how the project is being used in production, why it’s designed to complement existing LoRaWAN stacks like ChirpStack, and how future improvements are focused on lowering the barrier for new users rather than chasing complexity.
This episode offers a grounded look at the data layer of LoRaWAN systems, with practical insights for builders, operators, and businesses deciding how to store, query, and actually use the data their devices generate.
Links
Derek on LinkedIn
LoRaDB on Github