4 ms·
Out of pure curiosity, what are the common use cases for a fast in-memory database? Are they exclusive to server-side applications (e.g. caching)?
by remon 12y ago
Out of pure curiosity, what are the common use cases for a fast in-memory database? Are they exclusive to server-side applications (e.g. caching)?
- rmsaksida 12y agoCould be useful for a browser app which handles 'large' datasets, or for a mobile/desktop app as an SQLite replacement. Think of a messaging app which lets you search conversations client side with decent performance. It has a small footprint and some interesting features, so it might be a convenient DB for some apps even without strong performance requirements.
- ilghiro 12y agoCordova is a big one. The ability to have rich queries into some persistent data set is something that's difficult to achieve atm.
- joeminichino 12y agoIt's precisely why I created LokiJS in the first place, then it grew much bigger than that but yeah - that is where it all came from.
- nbrogi 12y agoBravo, Joe. Good job.
- delluminatus 12y agoYou can also use them in the browser to cache data to reduce server calls or improve client UI performance (a la meteor.js).
- tjelen 12y agoWell, it could be very useful as a more advanced "model" layer in browser-side MVC apps. I'm currently working on something that has a pretty complex data structure and simple JS objects/arrays simply don't cut it. LokiJS certainly seems worth looking into. The feature that looks especially promising is the ability to create Dynamic Views and to listen on notifications on these views.