# nosql cache csvs
- make it work over plaintext
- no serverside
- array of lines is basically the table
- algos rule, Red Black trees
- copy already optimized algorithms from
- SQLite
- org-roam
- obsidian
- redis
- mongodb
- store in IndexedDB for browsers
- write directly to plain text and then sync changes to cache

1) use some caching over csvs, convert plain text to some database internally, sqlite or indexed db or whatever
2) still use csvs directly, but implement algorithms from SQLite or every other serious DB, make it work with your plain text directly i can say that the second option still would lead to some form of caching, cause it is one of the optimization techniques used in serious RDBMS