11–20 of 24 posts
> Developing such a high quality power tool in such an open manner is honorable. Credit where credit is due, I would say their efforts are more than just "honorable", I could easily prefix that with an "extremely" and maybe add in a ", most excellent" afterwards.
i dont really into languages now. llm has solved this abstraction "perfectly". most of my query now are llm generated. i created custom api to connect llm to any databases im currently using.
i dont really into languages now. llm has solved this abstraction "perfectly". most of my query now are llm generated. i created custom api to connect llm to any databases im currently using.
If we had developed our tech in Python we’d be a world of hurt now as we scale.
I did consider tmducken in the beginning.
(Disclaimer: I maintain o11ylite)
I’m a big fan of tmducken. We use it heavily in our prod systems. That said, we’ve recently started exploring ducktape [1] in our new projects and have been really impressed with the performance. It also support more complex types on insertions and queries which has been helpful for us. Not affiliated with the project, but just wanted to show it some love since it’s a bit newer. It was created by an active contributo…
tmducken creator here, this is so rad to see - duckdb is a monster for sql on csv.
As a side note, thank you for all the work you have done in the Clojure ecosystem! Techascent’s data science packages was a major tipping point in my company’s decision to build our data science ecosystem in Clojure and has been wonderful to work with.
At Cronitor we use ClickHouse, but we're leaving it behind for our next product and building directly on Parquet and DuckDB. We think the future of observability in the AI age is self-hosted directly on NVMe backed by cheap and limitless object storage. I don't want to send customer conversations and agent thoughts to a giant multi-tenant borg SaaS database like Sentry or BetterStack.
> self-hosted directly on NVMe backed by cheap and limitless object storage.
How is that?! NVMe is a protocol for fast PCIE based local storage or NVMe fabric which is PCIe over network. Object storage(in the sense of S3, R2 etc) are usually networked horizontally scaling non posix bucketed storage. They are much much slower because of the network calls..
How would NVMe map to something like S3? And what for?
At Cronitor we use ClickHouse, but we're leaving it behind for our next product and building directly on Parquet and DuckDB. We think the future of observability in the AI age is self-hosted directly on NVMe backed by cheap and limitless object storage. I don't want to send customer conversations and agent thoughts to a giant multi-tenant borg SaaS database like Sentry or BetterStack.
I’m confused as an old school storage guy. > self-hosted directly on NVMe backed by cheap and limitless object storage. How is that?! NVMe is a protocol for fast PCIE based local storage or NVMe fabric which is PCIe over network. Object storage(in the sense of S3, R2 etc) are usually networked horizontally scaling non posix bucketed storage. They are much much slower because of the network calls.. How would NVMe map…
Impressive, you can really do a lot on a single node when it comes to big-data queries nowadays, I agree too many jump straight to a Spark cluster or something similar when you can just write a small script on a single node.