tylerhannan

Check the comments below or the OP. I think Ryadh does a great job of explaining the “why”

Why is that?

From the post

“ LibreChat remains 100% open-source under its existing MIT license Community-first development continues with the same transparency and openness Expanded roadmap to bring an even more enterprise-ready analytics experience. This proven playbook is the same one that we applied when joining forces with PeerDB to provide our ClickPipes CDC capabilities, and HyperDX, which became the UX of our observability product, ClickStack.”

Also, I work at ClickHouse, my email is super easy to figure out. Would love to alleviate concerns where I can.

We aren't a charity.

But, we are also a database provider.

Ryadh mentions some examples below where we have joined forces, incorporated code into ClickHouse Cloud (our commercial offering), and OSS has grown.

Time will tell (I can't predict future)...but I'm excited about the future of OSS LibreChat.

(disclaimer: I work at ClickHouse)

Nothing worse than having to update my IRC clients again ;)

(disclaimer: I work at ClickHouse)

At its simplest the team who was building that rad thing called LibreChat, now works at ClickHouse and build that rad thing called LibreChat.

Even simpler, the LibreChat team works at ClickHouse and are now my colleagues.

More complex, acquisitions can take a variety of "forms"...most importantly in these scenarios (and now I speak without knowledge of the deal structure) is making sure the team is paid, that copyright/trademark stuff is worked out, that OSS plans are discussed, and that everyone is excited to work together.

A database in isolation is meaningless.

Rather, people have to ask questions of it, and interact with the data. Increasingly, that is via AI tooling.

We've had a long-standing demo at llm.clickhouse.com (librechat, bedrock, anthropic).

(disclaimer: work at ClickHouse)

I actually took that picture a few years ago.

It's a fun story.

Our first swag shipment with the new colours had just arrived, the founders were in one place together for one of the first times, the weather wasn't terrible in Amsterdam for one day.

Not a pringles can. Rather they were stuffed in a shipping box that came from a warehouse, manhandled by customs, and thrown onto them for the purpose of taking the photo.

#startuplife eh?

Here is what the roadmap looks like at present.

There is a core of maintainers who care about Riak (after the company Basho ended many years ago) and it appears that most work has been moved into the OpenRiak repository.

https://github.com/orgs/OpenRiak/discussions/19

Heya, I'm Tyler. I work at ClickHouse, looking after Devrel (and, of course, don't speak on behalf of the whole company).

ClickHouse is, indeed, the best database to build observability tooling on. And, for those of our users who want observability "out of the box," HyperDX is the best solution.

As part of this, we are increasing our investment in observability across the board. For instance, we plan to continue building/improving ClickHouse core capabilities to support the observability use case (eg. inverted indexes, semi-structured data support, time-series table engine and more).

I look forward to seeing how other observability companies innovate atop ClickHouse. There is room for all of us to succeed.

Re. licensing. I can tell you that we are planning no changes at the moment. At one point we may align licensing on the HyperDX and ClickHouse open-source projects (Apache 2)...but that is TBD.

Do let us know if you have any questions...happy to answer.

(disclaimer: I work at ClickHouse and am super excited the PeerDB team is joining us)

ahhhh...space-filling curves.

With some of the recent work done with ClickHouse this has been an area I've had to learn about and, tbh, wish I had found this earlier.

Our CTO started using Morton curves for interesting purposes several months ago with initially piqued my interest and started me down the path.

https://reversedns.space/ (a map of the Internet) - Morton curve is used as a visualization tool;

https://adsb.exposed/ (a visualizer of air traffic) - Morton curve is used as a database index;

Our most recent release post dove into the usage of Hilbert curves in context of maintaining spatial locality for weather measurements

https://clickhouse.com/blog/clickhouse-release-24-06#hilbert...

Quite an interesting area of study and optimisation!

There is something about this that makes me so very happy.

A database is core to your infrastructure...finding out your database is going away is a horrifying situation. Finding out that the time you have to migrate is a few months. Agh.

As others will say, there are options. Rockset helpfully posts links to a bunch of comparisons on their website, and these alternatives include ClickHouse, Elasticsearch, Druid, etc.. https://rockset.com/real-time-analytics-comparison/

I'm inherently biased (as a member of the ClickHouse team). But do check ClickHouse out.

You can always come hang out in our Slack (clickhouse.com/slack) and, of course, the combination of hosted ClickHouse (clickhouse.com/cloud) and the open-source (github.com/clickhouse) may add a bit of comfort when your vendor up and disappears via acquisition.

I wanted one of these so much upon initial release.

I'd love the opportunity to actually try one in person but the last release was so hard to come by that it never quite happened.

Spelling fail...I'm sorry Jianfei!

It was pretty cool to watch this analysis play out internally to ClickHouse (note: I work at ClickHouse).

It was even cooler to see Vinay and Jianfie (authors) excitement to share the analysis, exploration, and detail.

lol.

I was waiting for that somewhere ;)

We hope not and try to keep in wire compatible for clients to interact (recently added dynamic reconfig, etc.)

It is definitely opinionated and influenced by our work...but not designed solely for it.

But, also, we continue to improve. Most notably in the work on Multi-group Raft - https://github.com/ClickHouse/ClickHouse/issues/54172

s/is a/was a/g

But more interesting, to me, is language adoption and familiarity by region.

I have a bookmarked dev.to article from 2020 that discussed programming language popularity by state - https://dev.to/eduecosystem/what-is-the-most-popular-program...

I'm uncertain if anyone has extrapolated that to more geographic regions. It would be interesting.

Definitely used in production ;) and at rather some scale.

It runs thousands of clusters, daily, both in CSP hosted offerings (including our own ClickHouse Cloud) and at customers running the OSS release.

Never accept any claims at face value and always test. But, in this case, it is quite battle-hardened (i.e. the Jepsen tests run 3x daily https://github.com/ClickHouse/ClickHouse/tree/master/tests/j...)

But yes, ZooKeeper is pretty amazing. We are building on the backs of giants.

I'd also argue the RAFT v. ZAB is an important production scale conversation. But, as the blog says, Zookeper is a better option when you require scalability with a read-heavy workload.

fundamentally, yep.

https://pradeepchhetri.xyz/clickhousekeeper/ talks about some experiments in exactly that vein.

"ClickHouse, Inc. is a Delaware company with headquarters in the San Francisco Bay Area. We have no operations in Russia, no Russian investors, and no Russian members of our Board of Directors."

Source - https://clickhouse.com/blog/we-stand-with-ukraine

Yep.

Generally, ClickHouse Keeper provides the coordination system for data replication and distributed DDL query execution for ClickHouse clusters.

It's a deep-cut reference. But it's one I am honoured you made.

:mug:

Thank you! We try ;)

++ agreed.

ClickHouse Keeper was released as feature complete in December of 2021.

It runs thousands of clusters, daily, both in CSP hosted offerings (including our own ClickHouse Cloud) and at customers running the OSS release.

Never accept any claims at face value and always test. But, in this case, it is quite battle-hardened (i.e. the Jepsen tests run 3x daily https://github.com/ClickHouse/ClickHouse/tree/master/tests/j...).

TBH, I don't think so.

I mean, I have worked and, and been guilty of tooling driven development (RiiR anyone?) .

But, also, in a comment below Alexey shares many of the reasons other than language. I think Oxia does a good job of sharing their approach in - https://github.com/streamnative/oxia/blob/main/docs/design-g...

(Alexey's comment, FYI, https://news.ycombinator.com/item?id=37677324)

Def.

I hadn't seen Oxia before but the idea, for their implementation, of making Zookeeper more like Bookkeeper was an interesting one.

Not right for ClickHouse needs but, IMO, a novel approach.

It does indeed.

Do note the docs page...

https://clickhouse.com/docs/en/guides/sre/keeper/clickhouse-...

In particular, it is necessary to enable the `keeper_server.enable_reconfiguration` flag. It is pretty exhaustive coverage but if there is an important use case missing, let us know!

Thanks for sharing!

If anyone has any questions, I'll do my best to get them answered.

(Disclaimer: I work at ClickHouse)