An Edge Computing Database Checklist

Understanding the unique requirements of the edge computing infrastructure is critical. As the Internet of Things (IoT) and edge computing continue to evolve, doors open for conducting business in new ways, especially when it comes to data management on the edge. Until recently, most data collected on the edge (at or near the collection point) was sent to the cloud or a data center for analysis and storage or discarded.

A new, third option has become available — databases that operate on edge hardware. However, not just any database will do. It should be a database that is specifically built for use in the unique environment of the edge.

A database that is truly built for use on the edge will empower organizations with the ability to store and process their data at or near the collection point, setting the stage for mission-critical and, possibly, life-saving decisions that can be made much faster and reliable, without the need to rely solely on the cloud.

There is no single database solution that fits all, rather each business should look to its unique case on the edge in order to determine the best choice. Having said that, there are a number of questions that should be asked when choosing a database for use on the edge:

• Can it guarantee data quality using transactional edge persistence (i.e., the data remains available after collection)?
• With what level of development efforts can it collect and store mission-critical data on the edge?
• Does it enable real-time IoT decision making? No, really, can it? Can it query live data fast enough to use that information to take action?
• How many major IoT operating systems and hardware platforms does it support? Can it run natively on the OS and hardware?
• Can it provide flexible/scalable data management, including portability, data partitioning, data coalescing, and replication?
• Does it support popular communication interfaces and multiple integrations?
• What communication protocols are supported to securely transmit selected data, such as strong encryption?
• What security features does it provide for all data stored at the edge?
• Can it use both SQL and NoSQL microservices to collect, query, and analyze data in real-time?
• What analytics tools can be integrated for use over actual real-time unstructured data?
• How big (or, rather, small in this case) is the footprint? (Hint: The smaller, the better.)