Dear Md. Adil ,

SQL databases due to their varied facilities is quite popular a choice for IoT solutions. IoT data requires diverse, customizable ingest pipelines that demand a database with a broad ecosystem. To meet these requirements, SQL is the best. With relational databases you can use schemas to aid with data modeling.

Regards,

Shafagat

Hello Md. Adil ,

IoT is a reasonably long set of results. Some TSDBs are available:

InfluxDB, OpenTSDB, GridDB, etc. They have all the version of the culture, so you can see if it is right for you. InfluxDB is popular but it is only possible to use a clustering for pay version. OpenTSD is pure oss and is IoT-focused and faster than InfluxDB, GridDB says. Perhaps you would prefer to search for one that ingests easily, based on your needs.

Regards,

Ahmed

The best IoT databases are:

1) Badger

2) Berekly DB

3) LevelIDB

4) ObjectBox

5) Realm

6) Redis

7) RocksDB

SQLite

For more details you can visit the following link:

https://objectbox.io/the-best-iot-databases-for-the-edge-an-overview-and-compact-guide/

Please follow the following link that describes the required steps to choose the beast DB for IoT

https://thenewstack.io/4-steps-to-select-the-right-database-for-your-internet-of-things-system/#:~:text=As%20a%20final%20note%2C%20Redis,and%20many%20other%20use%20cases.

The link below provides some insights to determining the best IoT database for the edge and provides some useful options.

https://objectbox.io/the-best-iot-databases-for-the-edge-an-overview-and-compact-guide/

Henry Nunoo-Mensah Thank You.

Reema Ahmad Thanks.

Shafagat Mahmudova Thank you.

Ahmed A. Mawgoud Thanks a lot.

Wisam Al Tameemi Thanks.

Enterprises and developers have many managed database services with different advantages to choose from. They should consider using AWS offerings such as Kinesis and DynamoDB, Azure Cosmos DB, MongoDB or Google Firebase. Organizations can use Kinesis to capture data in real time and send that data to NoSQL document database DynamoDB, which integrates with the Elastic MapReduce service that provides Hadoop and Spark-based analytic services.

If an organization does choose to work with a database-as-a-service provider, they should carefully consider the cost structure. AWS Kinesis Streams pricing is primarily based on shard hours; a shard hour allots 1 MB per second of input capacity and 2 MB per second of output. Customers pay $0.015 per shard hour. As for the data itself, Kinesis Streams uses PUT Payload Units to calculate total usage. Each unit comprises between one and 25 KB of data, so, for example, a 10 KB record is billed as one unit and a 30 KB record is billed as two. Customers are charged $0.014 per 1,000,000 units.

With AWS DynamoDB, the first 25 GB every month is free. Every GB after that is charged at $0.25 per month. As for operations, write throughput is charged at $0.0065 per hour per 10 units of write capacity. Read throughput is charged at the same rate for every 50 units. Note that data consumption in the cloud will exceed the raw size of your data and prices vary depending on region.

Azure Cosmos DB bases price on request units -- for example, the cost to read a 1 KB item -- whether the database operation is read, write or query. Provisioned throughput of 100 request units from a single-region account costs $0.008 per hour.

you can read this

https://internetofthingsagenda.techtarget.com/feature/Find-the-IoT-database-that-best-fits-your-enterprises-needs

For IoT devices any non relational database will be good to use. You should avoid using relational databases. The data from IoT devices would be stored as key value pair. IoT generates data from a myriad of sensors and transmitters, in this case a database will be less efficient if it is ACID complaint i.e. Atomicity, Consistency, Isolation and Durability are key factors for a Transactional database but not to an IoT database.

Shobhit Navani Okay. Thank you.

Ahmed Mohammed Bassal Thanks.

I recommend reading about json or key-value database, because you will store a lot of data