4 ms·
Just use PostgreSQL and don't evaluate anything. PostgreSQL can handle an enormous number of use cases, scales very well and can be made redundant with read-onl
by SomeHacker44 8y ago
Just use PostgreSQL and don't evaluate anything. PostgreSQL can handle an enormous number of use cases, scales very well and can be made redundant with read-only nodes too.
If you outgrow PostgreSQL, you have an excellent problem and are probably making tons of money. Don't waste mental power on this; just use it and focus on your business/product's core value proposition.
Or, read the article, which reaches the same conclusion with way more words. :)
- nine_k 8y agoFor RDBMSes, this. For write-intensive time series, or highly distributed, or graph databases you might consider other options.
- taffer 8y agoFor time series there is the Timescale extension for PostgreSQL.
- SomeHacker44 8y agoAs the sibling pointed out, there are extensions for that, that may be useful in PostgreSQL. It also is a good KVS, a document store, a queuing system, a pub/sub system, etc. While I usually add a message bus and a memory cache to a larger system, PostgreSQL can do all these things for you if you want to keep things simple.
- jdormit 8y agoIs there a good extension for postgresql that turns it into a graph database?
- taffer 8y agoThere is AgensGraph, but it seems to be a fork, not an extension.