3 ms·
I may have a project coming up that will include a document store component. It's in-house, with the maximum number of simultaneous users under 15, so scalabil
by reaperducer 7y ago
I may have a project coming up that will include a document store component. It's in-house, with the maximum number of simultaneous users under 15, so scalability that way isn't a concern.
However, the number of documents is large, and for some documents previous versions will have to be stored, as well.
With Mongo out, do you have any suggestions? Is PostgreSQL the best option here? I'm fairly new to this space.
- edoceo 7y agoI do like this, millions of record, prime fields in the table, then a jsonb column as the document-store. Just add a row for a new version. And extracting detail from jsonb is pretty easy, usable in SqL queries and materialized views
- kitotik 7y agoI just recently deployed a cockroachdb, and have been very happy with the results. For my use case, the JSONB columns are fantastic, and has much less deploy and admin overhead than Postgres.