@ascherbaum because I wouldn’t have to load everything to do anything.
To read 20 records I could load just those 20 files, that’s fast!
If I want to add a record I just add a new file, that’s fast!
If I make an edit I just edit a single tiny file, that’s fast!
In my use case I would never need to load more than like 150 records regardless of the size of the DB. I think loading many records would be the largest performance drawback of having one file per record.
My current implementation using one JSON file for the entire DB starts getting slow a few thousand records.
@orsvarn As to why JSON is slow, that's a whole different story. If you need to parse the entire JSON every single time, I can see that this doesn't perform well.
Add comment