Influxdb made the switch from Go to Rust
old.reddit.com
Influxdb made the switch from Go to Rust
1–10 of 162 posts
Re: Influxdb made the switch from Go to Rust
#2Seems like they have their priorities right. /s
Re: Influxdb made the switch from Go to Rust
#3Can someone explain what's the InfluxData's market? Or how they make/plan to make money?
If we speak about metrics, Prometheus just win.
Re: Influxdb made the switch from Go to Rust
#4tl;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" /s
Re: Influxdb made the switch from Go to Rust
#5Can 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.
Re: Influxdb made the switch from Go to Rust
#6tl;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!
Re: Influxdb made the switch from Go to Rust
#7I 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 better technical foundation.
Re: Influxdb made the switch from Go to Rust
#8Can 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 see Influx pop up a lot in communities like Home Assistant for doing time series data collection. I'm using Postgres for that myself (not a great experience but I knew that when I was too lazy to find alternatives during setup) but people seem very pleased with its performance.
I imagine similar dashboard services that don't necessarily work well in Prometheus are a good market for these types of databases. Prometheus is nice, but I don't think it's suitable for all Influx use cases (and vice versa).
Re: Influxdb made the switch from Go to Rust
#9> So this isn't the approach I'd recommend for this kind of project, but we started fresh from scratch.
wow, the from scratch rewrite. I can't even imagine that for a major piece of software
Re: Influxdb made the switch from Go to Rust
#10Can 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.