DB componentWriteMonkey 3 operates a hybrid system; JSON database with option for documents to be synced to independent files. That works OK for me.
Obsidian has a settings (workspace) file and, I think, a JSON file with some saved info. It automatically replaces both if they are deleted, but there's some database functionality at least during a session.
I think they may extend the database functionality. I will be watching carefully what they do with that. They have already reserved YAML front matter for themselves (I believe this is to expedite future plugin functions); I'm definitely not keen on this approach because it starts cluttering the file up with extraneous stuff - I'd prefer plugins were allowed to use a JSON file.
Simple for me to avoid plugins I don't like. If Obsidian itself goes in a direction I dislike, I'll stop using it or just have updates turned off.







