I discovered ClickHouse around 2017-18 and built a PoC to replace Elasticsearch: 5x better storage and qps, in a couple of weeks. 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.
Can clickhouse to search? If not why did you seek to replace elastic with it
Ten years of ClickHouse in open source
41–50 of 110 posts
Re: Ten years of ClickHouse in open source
#42Earlier quoted context omitted.
[flagged]
> ask a random stranger on the street if he's racist, and he will honestly say no, even if he actually simply does not realize it My lord you people are beyond patronizing. When people refer to "the Chinese" or "the Russians", we are taking about the nation state, not the people. And there are legitimate security concerns. Whether we should be adversial is another question. But we are.
I am wary of any supply chain attack and more so if the project is maintained by people with relationships in adversarial countries. The risk of exploitation outweighs the convenience.
Re: Ten years of ClickHouse in open source
#43If your data is too big for postgres, it seems like moving straight to Clickhouse is the best option. We have been through an whole array of distributed database technologies, and Clickhouse might be first one that doesn't have too many compromises.
What do you mean?
Postrgesql is a relational and row based db, ClickHouse is columnar
Clickhouse doesn’t replace postgresql:
Re: Ten years of ClickHouse in open source
#44Clickhouse is *really* gatekeeping the "zero copy replication" where you store data on object-storage and have high availability from the open source version.
I think that is just the nature of the open core business - but like most such businesses, they're not very clear about how that is what they are, pretending to be open source business instead.
Vc funded with recent rounds so 10 years hasn’t been enough time to make money
Re: Ten years of ClickHouse in open source
#45I discovered ClickHouse around 2017-18 and built a PoC to replace Elasticsearch: 5x better storage and qps, in a couple of weeks. 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.
Same we are also stuck with ES wish could migrate to clickhouse but not able to do so because of the legacy load.
What do you not like about ES?
Re: Ten years of ClickHouse in open source
#46Re: Ten years of ClickHouse in open source
#47If your data is too big for postgres, it seems like moving straight to Clickhouse is the best option. We have been through an whole array of distributed database technologies, and Clickhouse might be first one that doesn't have too many compromises.
What do you mean? Postrgesql is a relational and row based db, ClickHouse is columnar Clickhouse doesn’t replace postgresql:
Not to mention ACID and CAP and all that. I use clickhouse AND postgres. Clickhouse is not a replacement for postgres at all.
Re: Ten years of ClickHouse in open source
#48Earlier quoted context omitted.
[flagged]
> ask a random stranger on the street if he's racist, and he will honestly say no, even if he actually simply does not realize it My lord you people are beyond patronizing. When people refer to "the Chinese" or "the Russians", we are taking about the nation state, not the people. And there are legitimate security concerns. Whether we should be adversial is another question. But we are.
I agree about the legitimate security concerns, but not with "we're talking about the nation state, not the people". If life has taught me anything in the last few years, it's that normies are incapable of making this distinction, at least in the Old World.
Re: Ten years of ClickHouse in open source
#49If your data is too big for postgres, it seems like moving straight to Clickhouse is the best option. We have been through an whole array of distributed database technologies, and Clickhouse might be first one that doesn't have too many compromises.
What do you mean? Postrgesql is a relational and row based db, ClickHouse is columnar Clickhouse doesn’t replace postgresql:
You can keep "columnar" data in a row based database like postgres, it's just more expensive. But with little data that's fine and reduces infrastructural complexity. When you reach too much data it gets to a point where you then actually want to use the correct database for your usecase.
Re: Ten years of ClickHouse in open source
#50If your data is too big for postgres, it seems like moving straight to Clickhouse is the best option. We have been through an whole array of distributed database technologies, and Clickhouse might be first one that doesn't have too many compromises.
What do you mean? Postrgesql is a relational and row based db, ClickHouse is columnar Clickhouse doesn’t replace postgresql:
This is a extremely common issue that happens in growing firms.
You start off with everything in Postgres, it makes the most sense. Soon you realize some tables are growing really huge - usually some sort of time-series or log data reaching 10TB+. You can no longer fit it in one node. You can try you luck with some sharding extensions, but they add complexity to upgrades.
In that case it makes total sense to move these large tables off Postgres, and I think Clickhouse is a straight up replacement here. You can still keep your relational heavy tables in Postgres.
Yes it affects you ability to cleanly join data, and guarantee 100% consistency. With some smart application code, and schema design, you can replace parts of Postgres with Clickhouse for the big data problem.