Skip to main content

What is InfluxDB

InfluxDB is an efficient, reliable, and schema-less time-series database that can store time-series data.

It is a NoSQL database that provides high performance in terms of throughput, compression, and retention. InfluxDB can handle millions of time-stamped data points per second. InfluxDB includes support for real-time storage and analytics, IoT sensor data, and DevOps Monitoring. 

Some of the essential components of InfluxDB are :

Timestamp 

As InfluxDB is a time series database, time is an important essence in it. It stores time in the form of timestamps in the RFC3339 UTC format, which is yyyy-mm-ddThh:mm:ssZ. 

Fields 

InfluxDB has a concept of Fields that has components such as Fields keys of string types which are similar to the columns in RDBMS, Fields values that are the actual measured values of any types string, float, integer, or boolean and Fields set is a combination of Fields keys and values. 

Tags

InfluxDB has one optional component called Tags, which is similar to Fields except for the difference that both tag keys and tag values are of the typed string and hold metadata. So tags are used to add extra information about the measurements. 

Measurements 

Similar to the tables in RDBMS, InfluxDB has a concept of measurements that holds timestamps, fields, and tags together. It provides a way to describe the data in the set. 

Retention Policy 

The retention policy lets users define the period for which the data points should be stored in the database. 

Series 

Series is the collection of data points that have the same retention policy, measurement, and tag set. 

Points 

Similar to the rows in RDBMS, InfluxDB has a concept of Points that hold one or more fieldsets or tag sets in the same series with the same timestamp.

Comments

Popular posts from this blog

Building Scalable and Efficient Data Lakes with Apache Hudi

If you're looking to build a scalable and efficient data lake that can support both batch and real-time processing, Apache Hudi is a great tool to consider. In this blog post, we'll discuss what Apache Hudi is, how it works, and why it's a powerful tool for building data lakes. Apache Hudi is an open-source data management framework that provides several features to manage big data. It provides the ability to perform read and write operations on large datasets in real-time, while also supporting batch processing. With Hudi, you can also ensure data quality by performing data validation, data cleansing, and data profiling. One of the key advantages of Apache Hudi is its support for schema evolution. This means that as your data changes over time, Hudi can automatically update the schema of your data to accommodate these changes, without requiring any downtime or manual intervention. Another advantage of Hudi is its support for scalable and fault-tolerant data storage. Hudi p...

Top 25 Data Engineer Interview Questions

In my last post  How to prepare for Data Engineer Interviews ,  I wrote about how one can prepare for the Data Engineer Interviews, and in this blog post, I am going to provide the  Top 25 Basic   data engineer interview questions  asked frequently and their brief answers. This is typically the first round of the Interview where the interviewer just wants to access whether you are aware of basic concepts or not and therefore you don't need to explain it in detail. Just a single statement would be sufficient. Let's get started Checkout the 5 Key Skills Data Engineers need in 2023 A. Programming  1. What is the Static method in Python? Static methods are the methods that are bound to the  Class  rather than the Class's Object. Thus, it can be called without creating objects of the class. We can just call it using the reference of the class. Also, all the objects of the class share only one copy of the static method. 2. What is a Decorator in Python?...

What is CAP Theorem?

CAP Theorem states that a Distributed Database System can only have 2 out of 3 properties from Availability, Consistency, and Partition Tolerance . This means that every Big Data Engineer needs to do a trade-off between these three based on the use-case and Business requirements. It is very important for any Data engineer to understand the CAP Theorem and apply it when deciding the appropriate tools for the task in the hand. Let's discuss each of the properties in detail. 1. Availability   This condition states that every request (read/write) will get a response on Success or Failure. That means every node in the system must return a response in a reasonable amount of time. This could be only possible if the system remains operational all the time. Hence, the databases are time-independent as they should be available all the time. Therefore if any two records are added to the database we don't know which one was added first and the output could be either one of them. Now le...