InfluxDB is now InfluxData, a platform for time series data

The Influx team is doing great things - however from the perspective of someone who&#x27;s tried using InfluxDB in the last few months for a production app:<p>I really, really wish they&#x27;d hire 2-3 more database engineers to focus on the actual timeseries database, not nice looking tooling around it.<p>Simple things like incremental backups are still not working as expected in recent releases. Useful features from the 0.8 series still haven&#x27;t been ported. And tsm1 is a neverending effort it seems.<p>We&#x27;ve went back to Postgres for storing timeseries data since we didn&#x27;t feel confident to use InfluxDB in production.

I have been using InfluxDB (for throwing data into) and Grafana (for displaying pretty charts of that data). It&#x27;s pretty great.<p>I had no idea InfluxData forked Grafana and developed their own (currently closed-source) visualization tool named Chronograf. It looks like a InfluxData branded version of Grafana. Also interesting is that it&#x27;s the only closed-source element of their TICK stack.<p>Seems like there could easily be a conflict of interest here, such as new features of InfluxData only working with Chronograf and not Grafana.<p>grafana - <a href="http:&#x2F;&#x2F;grafana.org&#x2F;" rel="nofollow">http:&#x2F;&#x2F;grafana.org&#x2F;</a><p>chronograf - <a href="https:&#x2F;&#x2F;influxdata.com&#x2F;get-started&#x2F;#visualizing-data-with-chronograf" rel="nofollow">https:&#x2F;&#x2F;influxdata.com&#x2F;get-started&#x2F;#visualizing-data-with-ch...</a>

Good to see the forward progress. I needed to set up a metrics platform to serve tenants on a Mesos cluster, and picked InfluxDB over some alternatives for 3 main reasons: fairly reliable working state at the time (still using 0.8.8) with no dependencies, upward momentum, and stated priority of horizonal scaling. Looking back, it&#x27;s held up reasonably well. I&#x27;m admittedly disappointed that stable, horizontally-scalable clustering keeps getting pushed to the next release. To be fair, it&#x27;s hard, and the redisigns with the 0.9+ API and TSM tree are important - if you&#x27;re going to sell people on a dedicated time series DB it has to be really really good at it.<p>In the long run, the full ecosystem development here will pay off.

It&#x27;s interesting to see some competition in this space.<p>Basho, the maker of Riak has also moved from being a db company to being a data platform company. And they&#x27;ve also launched a time series version of Riak.

First, I really like the rebrand and wider focus. I think it will help people understand how your suite of tools work together (I just started playing with InfluxDB + Go yesterday and am loving it, and Telegraf seems a natural fit for another upcoming project too).<p>There&#x27;s a lot of mention about the ephemeral nature of time series data, but how is InfluxDB for storing permanent time series data? Are there any performance limitations I should be thinking about (aside from the limits of the hardware itself)?

Their stack is starting to look good, at least on paper.<p>I&#x27;m particularly interested in Telegraf. We&#x27;re using Prometheus for data collection and monitoring right now, and collection system is definitely the weakest part.

I&#x27;m a fan. Chronograf looks like an interesting alternative to Grafana - but it&#x27;s not open source :( Kapacitor looks neat as well, though it&#x27;s going up against stiff competition from Bosun.

I kind of prefered the old InfluxDB website but it may be a question of getting used to it. Either way I&#x27;m a fan, keep up the good work!

Any thoughts on the viability of using this platform in place of say data dog or librato?

All the best to Influx team. I see a good platform strategy here.

Wohoo! Looks like the full stack.