Open Alexhuihui opened 3 months ago
Scenarios without high performance and advanced features are feasible, as stated in the Why Not Use TinyDB? docs.
My team and I needed a way to update a database in a Git repository and trigger actions based on the DB updates. TinyDB works for that. It it similar to SQLite, but the DB updates are nicely human-readable with git
tooling. GitHub's web UI shows record additions, deletions, etc. My team needs transparency and approachability over raw performance at this stage of our application. We may outgrow TinyDB at some point, but we haven't hit that yet.
I took a look at the implementation, which uses full updates for writing and does not employ sequential file storage or ensure thread safety. It seems suitable only for educational purposes. I would like to know what production scenarios could utilize it.