4 ms·
> and the database for everyone else I also love postgresql but lets not get ahead of ourselves! It's great for SQL and as a traditional relational database, b
by diggan 6y ago
> and the database for everyone else
I also love postgresql but lets not get ahead of ourselves! It's great for SQL and as a traditional relational database, but there are plenty of use cases that are better served using other models (especially if you care about _time_ as a concept, then Datomic or crux is probably better suited) [although there are attempts on making bitemporality accessible in postgresql too, like https://github.com/scalegenius/pg_bitemporal https://github.com/scalegenius/pg_bitemporal]
- SOLAR_FIELDS 6y agoThere is a professionally developed time series extension for Postgres. I haven’t tried it personally but it might be “good enough” for quite a few use cases just like Postgres’ full text search can be “good enough” without having to bring in the machine gun that is ElasticSearch/Solr.
- diggan 6y agoRight, and it's probably "good enough" for most use cases. But, as always, it can't cover _everything_. I'm just making an argument against the sweeping argument that "postgresql is for everyone and everything"
- jjjensen90 6y agoI brought timescale (a postgres extension that brings time series to postgres) to my current IoT job, and it has been the biggest engineering win of my career. The tooling, community, extensions, and quality of postgres + very high performance inserts + reads has reduced costs for the business dramatically versus the previous cassandra + sql server setup. We have tens of billions of events in multiple timescale hypertables, with many thousands of inserts per second running on r5.xl nodes in k8s (4 vcpu, 30gb ram) and they don't break a sweat. So yeah, it's "good enough".
- paulie_a 6y agoCould you send me an email because my company is starting something similar
- diggan 6y agoI realize now in after hand that we're talking about two different things. You're mentioning time series data, I talked about bitemporal databases.