I think some form of persistent storage other than a config would be useful (e.g. #8#10).
PostgreSQL? Would be the most powerful option, but maybe a little bit oversized at this point.
SQLite? Is SQL just a file on the FS.
Text file? Most universal, additional packages likely not required and editable with every text editor. Also the least powerful and I think the most difficult option, because it would be completely custom.
My personal favorite at this point would be SQLite. Also I guess there are packages/modules, which can handle multiple SQL backends. With such a module it'd be possible to use SQLite now and easily switch the RDMS.
I think some form of persistent storage other than a config would be useful (e.g. #8 #10).
PostgreSQL? Would be the most powerful option, but maybe a little bit oversized at this point.
SQLite? Is SQL just a file on the FS.
Text file? Most universal, additional packages likely not required and editable with every text editor. Also the least powerful and I think the most difficult option, because it would be completely custom.
My personal favorite at this point would be SQLite. Also I guess there are packages/modules, which can handle multiple SQL backends. With such a module it'd be possible to use SQLite now and easily switch the RDMS.
https://github.com/sequelize/sequelize ?
I think some form of persistent storage other than a config would be useful (e.g. #8 #10).
PostgreSQL? Would be the most powerful option, but maybe a little bit oversized at this point.
SQLite? Is SQL just a file on the FS.
Text file? Most universal, additional packages likely not required and editable with every text editor. Also the least powerful and I think the most difficult option, because it would be completely custom.
My personal favorite at this point would be SQLite. Also I guess there are packages/modules, which can handle multiple SQL backends. With such a module it'd be possible to use SQLite now and easily switch the RDMS.
https://github.com/sequelize/sequelize ?
see #24