Cloud native and microservice architectures bring many advantages in terms of performance, scalability, and reliability, but one thing they can also bring is complexity. Having requests move between services can make debugging much more challenging and many of the past rules for monitoring applications don’t work well. This is made even more difficult by the fact that cloud services are inherently ephemeral, with containers constantly being spun up and spun down.

InfluxDB has over a dozen different client libraries to help developers work with time series data in whatever programming language they like best. The Python client library is one of our most popular options. It’s simple to learn, and working with InfluxDB in a language you’re comfortable with helps you get started doing powerful time series analysis quickly.

Commercial buildings produce 16% of carbon dioxide emissions in the US, and the EPA estimates that 30% of the energy used by these buildings is wasted. Energy efficiency in commercial buildings is a vital aspect of the transition to greener systems worldwide to fight climate change.

Joins are a common transformation in any query language, and as part of the effort to make Flux an increasingly valuable tool for our users, the engineers on InfluxData’s query team created, and continue to maintain, two separate join functions. And while these solutions have met some of our users’ needs, they both lack one key feature: support for outer joins.

User experience is the pinnacle of cloud technology. With cloud data centers handling 94 percent of all workloads, cloud optimization is vital. Users need fast, agile, scalable, and stable solutions over the long term. But how do you build these solutions? This is where cloud-native technology comes in. Cloud native computing provides the foundation for building, designing, running, and managing applications in the cloud.

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 wherever they are, to ensure their happiness, and accelerate Time to Awesome. This is the third in a blog series covering our product’s latest features — features that we think will save you time and effort when building with time series and InfluxDB.

After a mortgage payment, energy costs are typically the largest household expense. In my case it was an easy decision to install solar panels, but I wanted to perform in-depth analyses with historical data. Deploying monitoring sensors was straightforward; collecting and processing the raw data became the main challenge. Telegraf and InfluxDB are ideal choices for managing time series data. Although I had no prior experience, a Docker instance of Telegraf was onboarded in no time.

Developers are always trying to improve the reliability and performance of their software, while at the same time reducing their own costs when possible. One way to accomplish this is edge computing and it’s gaining rapid adoption across industries. According to Gartner, only 10% of data today is being created and processed outside of traditional data centers.

Smart energy IoT platforms are empowering consumers to track energy usage and even control spend based on their next bill’s forecast. Yet eSoftThings, a specialist in the Internet of Things (IoT) and artificial intelligence (AI), set out to push smart energy management even further, for both consumers and utility companies, through its IoT platform eSoftLink.

If you’re an InfluxDB user you might be considering migrating your workload to InfluxDB Cloud. You probably want to free yourself from the responsibilities associated with managing and serving your OSS account. Perhaps you are finding that you simply cannot scale your OSS instance vertically to meet your needs. Maybe you want to use all of the Flux functions that are available to you in InfluxDB Cloud.