Which problem? Of the massive breaking changes between 0.8 and later, and then between 1.x and 2.x? Not to mention InfluxQL to Flux?
Also, they did remove clustering in the open source version which was a very poor move from a PR perspective. And in my view, they have never recovered from it - years ago it was Prometheus vs InfluxDB for (non-SaaS) observability metrics, nowadays the only question is which backend for Prometheus to choose.
Not sure why the downvotes here, a database service misusing semantic version is itself a red flag in my opinion. If major releases don't indicate a breaking change I'm not as confident in what might be part of a minor or patch release.
> they did remove clustering in the open source version which was a very poor move from a PR perspective. And in my view, they have never recovered from it
I still remember this. We were ready to standardize on InfluxDB when we got a taste of their business practices.
Same, we were just about to choose InfluxDB, and ended up using it only for a niche low criticity scenario (VMware vSphere metrics, mostly for troubleshooting). We were never going to purchase Enterprise though, so they haven't lost anything outside of mindshare and champions, which can be evaluated to between 0 and infinity.
VictoriaMetrics. Don't have experience with InfluxDB, but had done rudimentary evaluation for popular backend. VictoriaMetrics stood out mainly due to low comparative operational maintenance.
Also, they did remove clustering in the open source version which was a very poor move from a PR perspective. And in my view, they have never recovered from it - years ago it was Prometheus vs InfluxDB for (non-SaaS) observability metrics, nowadays the only question is which backend for Prometheus to choose.