Advertisement
Advertisement
β‘ Community Insights
Discussion Sentiment
88% Positive
Analyzed from 468 words in the discussion.
Trending Topics
#clickhouse#using#timescaledb#data#open#long#version#made#same#worked
Discussion Sentiment
Analyzed from 468 words in the discussion.
Trending Topics
Discussion (14 Comments)Read Original on HackerNews
1. https://open.spotify.com/episode/0TBKDUhO0KihBxEzZqnQx1
In my current setup I was thinking on doing both: upgrading postgresql to timescaledb (to archive old data etc.), and to deploy ClickHouse in parallel. I'm still considering whether to go big on PeerDB to get ClickHouse mirror or just deploy it separately without additional fragility layer.
Would you not recommend using timescaledb at all? I definitely want to avoid alpha-quality software pain, since PostgreSQL is one of the most rock-solid parts of the stack at the moment.
Managers rejected it because it wasn't well known and was seen as "some database made by Russians."
On a personal level, it's quite sad to have seen that train coming so early and not been able to get on board.
Wow