4 ms·
I've found databases fascinating and tried various DB's as they come out. I always find some issue or caveat or problem and I decide in the end that Postgres g
by andrewstuart 6y ago
I've found databases fascinating and tried various DB's as they come out.
I always find some issue or caveat or problem and I decide in the end that Postgres gets most of the way there anyway and I return to Postgres.
Whenever I get tempted by a shiny new database I remind myself "don't bet against Postgres".
- akulkarni 6y ago+1000 Postgres. This is exactly why we chose to build TimescaleDB on top of PostgreSQL. Reliability, JSON, mature tooling, tons of connectors.
- gen220 6y agoThis is why I’m inherently skeptical of any database technology that isn't built on top of Postgres :) PG has mostly skipped the whole time series database trend until Timescale showed up. Still waiting waiting for the graph-db and git-db extensions! I think there’s been so much progress at the lowest level, that new SQL-databases might be kind of foolhardy to not build on top of PG at this point, especially if their main claim to fame is essentially a data type and some fancy indexing. I hope PG ends up more like Linux, and less like C++ or Java. :)