G2 has released their Fall 2022 reports, and we are thrilled to share that InfluxDB – the purpose- built time series platform, has once again ranked #1 in the G2 Grid for Time Series Databases. InfluxDB has also held its leading position in the Momentum Grid for Time Series Databases. The Momentum Grid® identifies products that are on a high growth trajectory based on user satisfaction scores, employee growth, and digital presence.
The number of applications and services increases every day as more application architectures move towards microservices or serverless structures. You can process this increasing amount of time series data with real-time aggregation or with a calculation whose output is a measurement or a metric. These metrics need to be monitored so that you can solve issues and make relevant changes in your system quickly. A change in a system can be captured and observed in many ways.
Flux is InfluxDB’s functional data scripting language. It’s made to query, process, analyze, and act on data. It’s very powerful and is built and optimized for time series. There are so many things you can do with Flux it can be hard to know where to start. This August, InfluxDB University launched a free Intermediate Flux course taught by experts that can take your Flux skills up a notch.
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 to meet developers where they are, to ensure their happiness, and accelerate Time to Awesome. This week, we are covering a product release that helps all InfluxDB Cloud UI users get more from their graphs.
If you’re an InfluxDB user you’ve almost certainly used the join() function. The join() function performs an inner join of two table streams. It’s most commonly used to perform math across measurements. However, now it is deprecated in favor of the join.inner() function which is part of the new join package. With the addition of the join package, Flux now has the ability to perform the following types of joins: A visualization of different types of joins from this article.
MQTT is becoming the standard protocol for applications that operate in environments where network connectivity is intermittent or unreliable, reducing bandwidth usage is a priority, or where hardware resources are limited. In this post you will learn about some specific use cases where businesses are seeing value from making MQTT part of their tech stack.
Databases are often the biggest bottleneck when it comes to application performance. Over the years a number of new database designs have emerged to help with not only basic scalability and performance but also to help improve developer productivity and make building certain types of applications easier. That isn’t to say these new databases are magical — there are always trade-offs being made and certain things are sacrificed for gains in other areas.
In an ideal world, developers would be able to release new products and features from development environments into production extremely fast while also not having to stress about breaking prod. Achieving this combination of development speed while also maintaining software reliability requires having the right toolchain and automation in place.
When it comes to IoT data, MQTT is a superstar. With so many IoT devices generating data out in the world, developers need ways to access it. After all, data lies at the heart of every application. But data doesn’t just magically manifest itself into your datastore, and building the right data pipeline can make or break an application. Data collection is not a one-size-fits-all problem to solve.
MQTT is a machine-to-machine communication protocol. Devices publish messages to a broker under specific topics, and other devices subscribe to those topics to receive information. It’s popular because it doesn’t take up a lot of bandwidth, so IoT devices with limited network connectivity can use it. MQTT works because of brokers. Each device sending and receiving data can communicate with potentially millions of other devices while only connecting to one broker.
