InfluxDB 3 Open Source Now in Public Alpha Under MIT/Apache 2 License

I’m excited to announce that InfluxDB 3 Core (open source) and InfluxDB 3 Enterprise are now in public alpha. I wrote a post with all the details here: https://www.influxdata.com/blog/influxdb3-open-source-public-alpha/

I’m happy to answer any questions here.

4 Likes

Hello, is my reading correct that InfluxDB 3 Core will store only 72h of data? and InfluxDB 3 Enterprise will store longer data?.

Then I if need to store longer data and query it I should use Enterprise one?
Or I’m missing something?

Thanks!

1 Like

@Paroles_Paroles InfluxDB 3 Core has a 72 hour query limit, but it does not delete data older than 72 hours. That data still persists. InfluxDB Core’s focus is on real-time and recent data and does not include a compaction service (compactor). Queries against uncompacted data are slower the more data a query loads, so the 72 hour query limit was introduced. The compactor optimizes aging Parquet by combining and “compressing” them and also makes querying historical Parquet files more performant, with the cost of additional overhead to run the compactor.

With that said, this is an alpha and things could change. InfluxDB 3 Core doesn’t delete data older than 72 hours. All data is stored in Apache Parquet format, so you could still access that data using other tools that can query Parquet. But those Parquet files are not compacted. If you were to upgrade to InfluxDB 3 Enterprise, you could then query all of your written data and the compaction service included with Enterprise would begin compacting your historical data.

oh my goodness this is amazing, thank you!

this link is not working for docker: quay.io/influxdb/influxdb3-core:latest

https://docs.influxdata.com/influxdb3/enterprise/get-started/quay.io/influxdb/influxdb3-enterprise:latest

But looking great in grafana so far when running it in windows

HI @scott,
When we mention a query limit of 72 hours, does that mean we can only query 72 hours’ worth of data at a time?
Currently, we are using InfluxDB version 2.7. If we plan to upgrade to InfluxDB 3.0 and perform historical queries, are we required to upgrade to the Enterprise version?

No, it means you can’t query data older than 72 hours with InfluxDB 3 Core. For historical queries, you will have to upgrade to InfluxDB 3 Enterprise.

There has been discussion around offering a personal/hobbyist Enterprise license that would give you data compaction, enable historical queries, and possibly grant access to other Enterprise-specific functionality. I don’t have any other details because it’s just been discussion and we’re still in alpha.

1 Like

Huge thanks for clarifying the 72-hour query limit @scott . I think there was some confusion and this helps understand it better.

2 Likes

Hello, first of all thank you for your work.

I’m a bit confused with all the product names of Influxdb3. (Core, Enterprise, Edge, Community …) Are the advantages/disadvantages of the individual versions known and what the development plans are?

I would also like to know, as the 72 hours in the Core version are not enough for me, how much the Enterprise version will cost later or whether it is better for private users to wait for the Edge/Community version - should it still be available!? Many thanks

@Tundril “Edge,” “Community,” and “Pro” were all working names for the this particular architecture of InfluxDB 3. Community was ultimately dropped and “Edge” was named “Core” and “Pro” was named “Enterprise”.

So the full InfluxDB 3 line of products looks like this:

  • InfluxDB 3 Core: OSS, real-time or recent data engine, run by a single service
  • InfluxDB 3 Enterprise: Commercial, real-time, recent, or historical data engine, run by a single process, HA-capable
  • InfluxDB Clustered: Commercial, self-managed, distributed architecture, designed large write and query workloads on your own infrastructure
  • InfluxDB Cloud Serverless: Commercial, fully-managed, multi-tenant, distributed architecture, best for small to medium workloads
  • InfluxDB Cloud Dedicated: Commercial, fully-managed, single-tenant, distributed architecture, designed for large write and query workloads

Pricing is still being finalized, but more information should be available as we prepare for general availability.

The “Community” version is no longer planned, but, as mentioned above, there has been discussion about offering a personal/hobbyist license for InfluxDB 3 Enterprise. No concrete decisions have been made yet since we’re still in early alpha, but it is being considered.