Hi,
I am writing a small registration web server using abmaterial. I store users' info on a single json file.
I think it is too simple to use json as my database, so I sought to keyValueStore. SQLite+keyvalue sounds great. But my app just increases from 6mb to 12mb and costs running memory. Also, the code is not as easy to maintain as a json file.
The keyValueStore is like an in-memory NoSQL datebase based on SQLite. As I am not a professional, I'd rather to store on disk directly.
So I decide to roll my code back. Using Json to store data is fine right now. Maybe I should store users' info on separate files based on user's id, which can improve concurrent access.
I am writing a small registration web server using abmaterial. I store users' info on a single json file.
I think it is too simple to use json as my database, so I sought to keyValueStore. SQLite+keyvalue sounds great. But my app just increases from 6mb to 12mb and costs running memory. Also, the code is not as easy to maintain as a json file.
The keyValueStore is like an in-memory NoSQL datebase based on SQLite. As I am not a professional, I'd rather to store on disk directly.
So I decide to roll my code back. Using Json to store data is fine right now. Maybe I should store users' info on separate files based on user's id, which can improve concurrent access.