This article was priginally published on the CNF blog and is written by Cameron Pavey. Scroll down for the author’s bio. Docker is an increasingly popular choice for businesses dealing with containerized applications. However, as with any new technology, Docker introduces complexities that need to be managed. Some of these complexities relate to infrastructure and application monitoring.

A look at what Apache Arrow is, how it works, and some of the companies using it as a critical component in their architecture. Over the past few decades, leveraging big datasets required businesses to perform increasingly complex analysis. Advancements in query performance, analytics, and data storage are largely a result of greater access to memory. Demand, manufacturing process improvements, and technological advances all contributed to cheaper memory.

This article was originally published in The New Stack and is reposted here with permission. Arrow makes analytics workloads more efficient for modern CPU and GPU hardware, which makes working with large data sets easier and less costly. One of the biggest challenges of working with big data is the performance overhead involved with moving data between different tools and systems as part of your data processing pipeline.

If you are working with large amounts of data that will primarily be used for analytics, a column database might be a good option. There are a lot of different options when it comes to choosing a database for your application. A common discussion seems to be the high-level SQL vs. NoSQL database argument of whether data should be stored in a relational database or in a NoSQL alternative like key-value, document or graph databases.

With native SQL support coming to InfluxDB, we can broaden the scope of developer tools used to analyze and visualize our time series data. One of these tools is Apache Superset. So let’s break down the basics of what Superset is, look at its features and benefits, and run a quick demo of Superset in action.

Red Hat is a global leader for open source enterprise IT solutions with a portfolio of products that includes hybrid cloud infrastructure, middleware, cloud-native applications, and automation solutions.

At this year’s InfluxDays event, the capabilities of InfluxDB took center stage. It’s not enough to simply deploy a technology platform and hope people will use it. This isn’t a Kevin Costner movie. That’s why it’s helpful to talk about specific use cases, their typical challenges, and how InfluxDB can address those challenges. Fortunately, that’s just what Influxer Charles Mahler did for network monitoring.

At some point if you’re working with data, you’ll probably want to be able to visualize it with different types of charts and organize those charts with dashboards. You’ll also need somewhere to store that data so it can be queried efficiently. One of the most popular combinations for storing and visualizing time series data is Grafana and InfluxDB.

I recently chatted with one of our InfluxDB Cloud customers, Rune Labs, to discuss how they’re using this purpose-built time series platform. Every customer has a unique story — I love sharing their stories as well as their Telegraf, InfluxDB, and Flux tips and tricks. Keep reading to learn about Rune Labs’ approach to precision neurology, and learn from Engineering Manager Carolyn Ranti how they are using InfluxDB to collect sensor data.

With the release of InfluxDB’s new storage engine for InfluxDB Cloud, InfluxDB Cloud now supports SQL. This is because the updated InfluxDB uses the Apache Arrow DataFusion project as a key building block for its query execution engine. DataFusion’s sophisticated query optimizations support near unlimited cardinality data in InfluxDB Cloud.