Cole Bowden

BIG NEWS from #InfluxData and @awscloud. We’re expanding InfluxDB 3 on Amazon Timestream for InfluxDB with support for clusters up to 15 nodes, unlocking massive ingestion throughput, higher query concurrency, and true workload isolation for the most demanding time series workloads. We’re also introducing a seamless migration path from InfluxDB 3 Core to Enterprise, so teams can scale from a single node to enterprise-grade clusters without downtime or rearchitecting their system. As telemetry grows from minute-level metrics to high-resolution, real-time data streams, developers need infrastructure that scales just as fast. Read more from our CMO, Pat Walsh: bit.ly/40AfQWQ

Struggling with sensor ingestion, schema design, or cardinality issues in your IoT stack? Join #InfluxDB experts Ian Clark, @suyashcjoshi, and @InfluxCole for a live open Q&A on March 17th. Ask us anything about edge ingestion, dashboards, retention strategies, and more. bit.ly/3Nhydg9

@rohit____jadhav As a heads up, InfluxDB 3 has no issues with high cardinality - by eschewing indexing, it runs fine with unlimited cardinality.

to Analytical DB to production reality. The Initial Thought: TSDB Common wisdom says use a Time Series DB (InfluxDB/TimescaleDB) for metrics. But for tracking millions of unique users, they have a major weakness: High Cardinality.

The "Ideal vs. Practical" Engineering Thread 🧵 Recently I was assigned to figure out which time series database to show usages to end users over some period of time(like a month)