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.
Labels:

Comments

Post a Comment

Popular posts from this blog

How to migrate the data between AWS and Google Cloud Platform

There are several ways to migrate data between Amazon Web Services (AWS) and Google Cloud Platform (GCP). Here are three common approaches: Use a Cloud Data Integration Tool: Both AWS and GCP offer a range of tools that can help you move data between the two platforms. For example, AWS Data Pipeline is a fully-managed data integration service that can extract data from various sources, transform the data as needed, and load the data into a destination system. On GCP, Cloud Data Fusion is a similar tool that can help you build, execute, and monitor data pipelines between various data sources and destinations. You can use these tools to create a data pipeline that moves data between AWS and GCP. Use a Command-Line Tool: Another option is to use a command-line tool, such as aws s3 cp or gsutil, to transfer data between AWS S3 and GCP Cloud Storage. For example, you can use aws s3 cp to copy data from an S3 bucket to your local machine, and then use gsutil cp to upload the data to Cloud ...
Post a Comment
Read more

Difference between Union and Union All in SQL

You might be using Union or Union All in your SQL code while doing Data Analysis or building Data Pipelines. Ever wondered what is the difference between them and how using one over another can be more efficient? Yes, there is a small yet significant difference between Union and Union All. Let's look at that by understanding each of them individually. 1. Union All  Union All basically allows you to concatenate the table that has a similar structure of tables. The important condition to have Union All of the tables is that both the tables should have the same number of columns. So when you take Union All of two tables what it does in the background is it directly joins the tables without removing duplicates or redundant records.   2. Union  Union is also similar to Union All except one difference that it removes the duplicates records before taking the Union of the tables.  There is one disadvantage of Union over Union All, that since it removes duplicated records bef...
Post a Comment
Read more

What is Shuffling in Spark

Shuffling in Spark is a mechanism that Re-Distributes the data across different executors or workers in the clusters.  Why do we need to Re-Distribute the data?    A) Re-Distribution is needed when there is a need of increasing or decreasing the data partitions in the situations below: When the partitions are not sufficient enough to process the data load in the cluster When the partitions are too high in numbers that it creates task scheduling overhead and it becomes the bottleneck in the processing time. Re-Distribution can also be achieved by executing the shuffling on existing distributed data collection like RDD, DataFrames, etc by using the "Repartition" and "Coalesce" APIs in Spark. B) During Aggregation and Joins on data collection in Spark, all the data records belonging to aggregation or join should reside in the single partition and when the existing partitioning scheme doesn't satisfy this condition there is a need to re-distributing the data in in...
Post a Comment
Read more