I want to be excited, because this is such a smart combination of excellent utterly modern zero-copy data technologies. I love that Influx is using such a strong base of tech to build this.<p>> <i>These products are built on more than four years of development and powered by the FDAP stack—Apache Flight, DataFusion, Arrow, and Parquet—and delivered on our rebuilt time series database architecture.</i><p>So awesome.<p>Its a bit harder to be quite as merry when the list of things that are enterprise only is so long. I know companies need to pay the bills, & don't begrudge them their decisions, but this still hurts;<p>> <i>InfluxDB 3 Enterprise adds historical query capability, read replicas, high availability, scalability, and fine-grained security.</i><p>Having 72 hour max limit, single instance only, without high availability, and reduced security each seem like really big feature gates to deny the open source edition. Any even mildly serious adopter is probably going to need at least one of these.<p>I want to stay positive & hopeful & still am, but this feels like one of those really narrow open core strategies that makes me nervous.
> InfluxDB 3.0 open source will be called InfluxDB 3 Core, a recent-data engine persisting Parquet files and enabling queries against the last 72 hours of data. Development of Core will carry on under the permissive MIT or Apache 2 license<p>> InfluxDB 3 Core gives developers a new tool for time series data management—a high-performance recent-data engine optimized for querying the last 72 hours of data. This focused approach enables Core to deliver exceptional performance for real-time monitoring, data collection, and streaming analytics use cases. By optimizing specifically for this pattern, we’ve achieved query response times under 10ms for last-value queries and under 50ms for hour-long ranges.<p>The limitation of 72 hours of data is a bit disappointing. There are use cases that don't require 50ms query response times, but instead need longer on-prem storge. InfluxDB 1.X and 2.X supported these well. Would it be possible to reduce query performance and extend data retention?<p>Is there any guidance on a planned EOL for InfluxDB 1.X and 2.X once Core reaches GR?
It's a shame the v3 OSS version is simply not a functional alternative to InfluxDB v1 and v2. I understand money needs to be made, but not even being able to query further than 72 hours in the past... But seeing the changes from v1 to v2 to the development around v3, I am not surprised. InfluxData has been moving more and more into the direction of enterprise, honestly more surprised there is an OSS offering at all
Creator of InfluxDB and cofounder and CTO here. Happy to answer any questions. We're very excited to finally have this release in public. It's been years in the making and we hope to iterate quickly on any feedback.