Would be great to see an in- depth blog post by Andrew and team about Rust, the bad and the good. They didn't just build a system but one that was optimized for performance. What were the major challenges during the rewrite? Have you optimized CI build times?
Influxdb made the switch from Go to Rust
11–20 of 162 posts
Re: Influxdb made the switch from Go to Rust
#12tl;dr - No garbage collector - Fearless concurrency (thanks Rust compiler) - Performance - Error handling - Crates - they thought they were gonna use C++ and wanted interop (ended up not using C++?) - ecosystem: Apache Arrow DataFusion - "I thought that if we're going to rewrite most of the database anyway, we might as well do it in the best language choice in 2020" But the real reason might be: "Rust good, Go bad" /…
Rust gets you on the frontpage!
Go does too. Those two feel like the most hyped languages currently on HN.
Re: Influxdb made the switch from Go to Rust
#13Can someone explain what's the InfluxData's market? Or how they make/plan to make money? If we speak about metrics, Prometheus just win.
Influx is a wholesome solution where Prometheus is just the time series database
Re: Influxdb made the switch from Go to Rust
#14Can someone explain what's the InfluxData's market? Or how they make/plan to make money? If we speak about metrics, Prometheus just win.
I am about the biggest Prometheus stan that you can find, but I will not mock or denigrate influx db. They are a runner-up, but there is room in this market for runner-ups, and their feature set does match some that Prometheus is not good at.
Don't get me wrong, I don't denigrate Influx DB.
They have some interesting features that prometheus doesn't have, I just don't think that this features can lead to a mass adoption(and money).
Let's put this way: is there any killer feature that can ditch most of the Prometheus installations in their favor?
Re: Influxdb made the switch from Go to Rust
#15Can someone explain what's the InfluxData's market? Or how they make/plan to make money? If we speak about metrics, Prometheus just win.
Influx is a wholesome solution where Prometheus is just the time series database
Maybe i miss something, but the version 3 is just the database, they abandoned the TICK stack some time ago.
Re: Influxdb made the switch from Go to Rust
#16People are not talking that InfluxData is NO more just a time series database, this isn’t just a language change but feature additions and with the level of massive dependence on C++ libraries it’s pretty foolish to continue using Go
Re: Influxdb made the switch from Go to Rust
#17https://github.com/influxdata/influxdb
The non-reddit link target
Re: Influxdb made the switch from Go to Rust
#18I love influx but damn do they like moving (too?) fast and quickly changing stuff. In a way, it's pretty cool since it means that they don't get stuck with bad decisions for backwards compatibility reasons, but it's a bit of a roller coaster for users. Not sure what's the best solution though. Having a "stable" but fundamentally limited product (I guess influxdb v1) or breaking stuff in hopes of ending up with a way…
Sounds like tech I wouldn't wanna depend on.
Re: Influxdb made the switch from Go to Rust
#19Can someone explain what's the InfluxData's market? Or how they make/plan to make money? If we speak about metrics, Prometheus just win.
As is tradition, hosted service: https://www.influxdata.com/influxdb-pricing/ Basically either you manage it yourself, or you pay them to do Serverless/Dedicated/Clustered hosted setup for you.
Yeah, I know, but there are a lot of competition in this field.
Every cloud provider, Grafana and other players have their own managed Prometheus compatible solution.