InfluxDB is a timeseries database. Currently at version 3.0. Is being slowly killed by InfluxData.<p>TLDR:<p>InfluxDB 3.0 is deprecating Flux (introduced in 2.0). Dropping continuous queries as a feature.
Source: https://community.influxdata.com/t/is-flux-being-deprecated-with-influxdb-3-0/30992/6
Archive: https://web.archive.org/web/20230821062059/https://community.influxdata.com/t/is-flux-being-deprecated-with-influxdb-3-0/30992<p>------------------<p>InfluxDB 0-1.x gained popularity as simple timeseries database that had SQLike query language, easy to use, adequate performance. During the inception ~2014 it was marketed being built by GO.<p>Along comes 2021 and the InfluxDB 2.0 that introduces new query/scripting langue "Flux". InfluxData is highly promoting that new scripting language built into the database. For some users this is seems cool feature but for some derivation from known basics (SQL) feels odd.<p>moving forward 1-2 years. InfluxData starts to market their new database engine IOx. Written in Rust. Their blog is filled with IOx or Rust articles.<p>2023 InfluxDB 3.0 is released. This is at the moment closed sourced. Open source is promised ~2024. This is fine.<p>But now it seems that in their support forums it has been revealed that theid "killer feature" from 2.0 - FLUX is being deprecated. See https://community.influxdata.com/t/is-flux-being-deprecated-with-influxdb-3-0/30992/6 and https://web.archive.org/web/20230821062059/https://community.influxdata.com/t/is-flux-being-deprecated-with-influxdb-3-0/30992<p>This is revealed in support forum comments! Most of the 2.0 do not know how screwed they are or going to be.<p>This is baffling as InfluxData developing database as some random Javascript (NPM) library where breaking changes are frequent. This is unexpected as database "world" is considered having to favor stability.<p>It seems that Influxdata is being led by people that are following the latest trends and led by them. When ~2013 Go was the RAGE the database was marketed as built by GO. Along comes the Rust and they switch to it.<p>All it seems to be just to rake in the series N investors cash. Damned by the stability of the product and their user base.<p>----<p>p.s. I am running 40+ InfluxDB 1.8 servers and was holding back to upgrading to InfluxDB 2.0 as for our queries the Flux language was 3-10x slower. Now reading that Flux is being deprecated and continuous queries go away it makes me feel that this product is failing that that company is going away in couple of years.<p>I predict that in couple of years InfluxDB 4 or 5 will be in whatever language will replace Rust hypetrain (if InfluxData still exists by that time).
InfluxData is Venture Funded company which is in search of sustainable business model. Things have not been doing great for them<p><a href="https://www.teamblind.com/post/InfluxData-Layoff-jc2cUv8u" rel="nofollow noreferrer">https://www.teamblind.com/post/InfluxData-Layoff-jc2cUv8u</a>
<a href="https://www.reddit.com/r/influxdb/comments/14vph93/all_data_deleteda_warning_for_those_using/" rel="nofollow noreferrer">https://www.reddit.com/r/influxdb/comments/14vph93/all_data_...</a><p>This is the danger with single vendor Open Source projects, which have not yet reached sustainability.
If InfluxDB 2.0 came out in 2021, you have had plenty of time to worry about long term perspectives and the low performance queries you mention before the InfluxDB 3.0 release.<p>What are the plausible InfluxDB replacements you are considering for your applications?