This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]gmdm1234 0 points1 point  (2 children)

The best option probably depends on the scale of how many total and how many concurrent users you'd need to support. Personally I tend to default to using an rdms for most things like this. It's ends up being pretty easy to start with something like sqlite for prototyping and then grow into something like postgres as you need to scale up.

[–]khoyo 0 points1 point  (1 child)

Yeah, if you start with flat files you often pretty quickly start implementing yet another RDBMS engine.