3 ms·
On the other hand, microcontrollers typically have ample Flash storage for code, but very limited amounts of RAM. Instead of making everyone rewrite their own m
by teraflop 11y ago
On the other hand, microcontrollers typically have ample Flash storage for code, but very limited amounts of RAM. Instead of making everyone rewrite their own memory-efficient data structures, it might well make sense to have a single, general-purpose implementation -- even if some of the code goes unused in a particular application.
- listic 11y agoWell, if you can really make SQL work well within such constraints and be convenient to use - I see no harm in it.
- niutech 11y agoKeep in mind that the Flash storage has a limited number of writes, so keeping frequently changing data in memory and choosing a right data structure can be crucial for your data's life span. SQL is not an universal solution for all use cases.
- geedy 11y agoYou are not wrong, but consider that the problem may be handled a number of ways. Once I move to storing everything through IonDB, you will be able to choose key-value stores that could wear level, should one be implemented. Such algorithms have been suggested in other works. Furthermore, if the device supports a storage API that already does wear levelling, you than a SQL layer on top should not hurt.