![]() ![]() Most notably, it doesn’t have built-in encryption for data at rest or in transit, let alone at 128-bit or above. However, SQLite has many drawbacks compared to a commercial, enterprise-grade embedded database. ![]() ![]() Settling would be an equally poor choice. ![]() It handles most SQL API calls, so it’s also standard. SQLite is able to run on a device to support fully optimized use of local compute resources, providing an application with the ability to handle local data management – yet offering the same set of APIs calls for a web-based version of that same app, or even work on both the native and web components of a more complex app. Why? Unlike memory allocation and use of flat files, which provide little standardization, built-in indexing or other real data manipulation, SQLite provides baseline database support for Edge Intelligence. First off, SQLite is a far better than a combination of temporary memory allocation and flat file systems, an approach I’d never recommend to anyone I call a friend. While this is not the first or the largest potential breach point found in Open Source data management – after all, the Heartbleed virus in 2014 that took advantage of OpenSSL probably holds both of these records – because this vulnerability is associated with SQLite, a database that is near ubiquitous in mobile native and web-based apps, and its APIs, we should brace for the knee-jerk reaction: perhaps data shouldn’t be stored locally on Edge devices and everything should be done in the Cloud, where it’s assumed to be more secure (my, how times have changed). This could very well be where we are now with localized and embedded data management for Edge devices.Ĭase in point, over the weekend a very serious security vulnerability was discovered in SQLite and the Web bundled version of SQLite in Chromium (the Open Source roots for Google Chrome). Let’s not forget that 10 years ago, each security breach in the Cloud generated a sense of panic and perhaps slowed adoption of Cloud services. There have been several studies and surveys undertaken over the last few years that clearly show a far larger number of security vulnerabilities in IoT and Mobile device-based software than on more mature desktop or laptop platforms, let alone software running on servers in the data center. Unfortunately, what’s equally unavoidable is that security vulnerabilities and opportunistic attacks that target these weaknesses will increase for the foreseeable future. It’s a foregone conclusion that data associated with these applications will mushroom. There will be countless mobile and IoT – taken as a whole, Edge scenarios – where a native application will be a better approach than a web-based application, or where it would be inefficient/potentially less secure to send raw data back from IoT collection points – rather than process the data and locally store or erase the input data.Ĭomplexity of process and workflow at the Edge, ability to run analytics at the point of action, and working in disconnected modes or with spotty connections are all examples of why you will need local data storage and therefore a local database. It’s indisputable that Edge Intelligence will grow, whether that’s mobile applications running on Smartphones, IoT applications running in Smart Cars (or the underlying sensors), in the entertainment center, navigation systems, etc. Face the inevitable: Local persistent data at the Edge will happen ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |