Storage. Move back to SQL? - Githubissues

mpdroog / invoiced

Simple hour registration + invoice generator.

BSD 2-Clause "Simplified" License

13 stars 5 forks source link

Storage. Move back to SQL? #7

Closed mpdroog closed 5 years ago

mpdroog commented 7 years ago

Store data in CockroachDB?

Why stay with BoltDB:

Simpler code, no need to convert structs to DB flat struct;
No external deps
Easily 'scale' as data can be separated in buckets

Motivation to move away from BoltDB:

Not easy to quickly do a custom query to get revenue numbers out;
Replication between nodes?

mpdroog commented 7 years ago

Or even better store as plain/text on the filesystem?

Easier to manually adjust files if I want to;
Best protection against corruption;
Can use 'submaps' to have the same as buckets;
Simply add file.meta.toml to add 'metadata' to files or directories;
Integrate with Git for simple auditing (revisions)
(Ab)use Git for replication between nodes?

Searching through the data requires an indexer anyway, maybe have a look @ http://www.blevesearch.com/ or write to SQLite for advanced query power?

mpdroog commented 5 years ago

We're using plain/text with Git by now.