According to the old adage, life’s a journey not a destination. The same can be said for software. It’s unlikely that any developer would ever say that something they built was truly done. There are always bugs to squash, features to add, and updates to implement. As a company intensely focused on time and the context of time, it comes as little surprise that these themes played a significant role in Paul Dix’s presentation for InfluxDays.
This week at InfluxDays we announced that Flux 1.0 is coming soon. Version 1.0 of Flux lang is a commitment to no longer make breaking changes to the Flux language. Importantly, today’s Flux scripts will work on Flux 1.0, and no breaking changes will be introduced between now and the release of Flux 1.0. Along with version 1.0, we have some features we are also releasing soon. Here are the features we have coming and a short explanation of why you might want to leverage them.
Last week InfluxData announced IOx, the new time series engine for InfluxDB. We’ve revisited the core of our database to achieve big things with the underlying technology. Users can expect higher performance and more options for querying data. Here’s a quick intro to some of the most exciting things coming with InfluxDB IOx.
SAN FRANCISCO, November 2, 2022 – Today, InfluxData, creator of the leading time series platform InfluxDB, announced significant product enhancements at InfluxDays 2022, its annual developer and community event. New features including InfluxDB Script Editor, Telegraf Custom Builder, and Flux 1.0 support developers working with time series data, allowing them to do more with less code.
The InfluxDB platform has evolved a lot over the past decade. But with every innovation we’ve added to the platform, the focus behind our efforts has remained the same: Build cool stuff for people who build cool stuff. What we mean by this is we want to make it incredibly easy for users to build valuable applications with their time series data. We do that by offering a wide range of tools, features, and resources that meet builders on their terms.
We love to write and ship code to help developers bring their ideas and projects to life. That’s why we’re constantly working on improving our product in sync with developer needs to ensure their happiness and accelerate Time To Awesome. This month is very special. We now have a new engine that significantly increases the “horsepower and torque” for InfluxDB.
Native MQTT eliminates the need to write custom code, orchestrate additional technology layers or incorporate additional hosting services. MQTT is a powerhouse within the Internet of Things (IoT) space. Its pub/sub model and lack of defined payload structure make it infinitely adaptable to the needs of modern sensors, devices and systems. IoT data is also time-series data.
This article was originally published in The New Stack and is reposted here with permission. Working with geo-temporal data can be difficult. In addition to the challenges often associated with time-series analysis, like large volumes of data that you want real-time access to, working with latitude and longitude often involves trigonometry because you have to account for the curvature of the Earth. That’s computationally expensive. It can drive costs up and slow down programs.
How to set up a basic React app, query data from InfluxDB Cloud and use the queried data to populate results using Apache ECharts.
One of the significant features announced with InfluxDB IOx is native SQL support. Even if SQL isn’t the lingua franca of the computing world, there are no doubt those that could make a case for it. There seems to be some dialect of SQL in virtually every corner of the internet.
