Hello everyone,
I’m happy to announce that the next minor version of ReductStore has been released. For the last month, we worked hard to improve the user experience when querying data from the database. And in this release, we deliver two important features:
Let me show you how it works in detail and how you can use it.
ReductStore provides an HTTP API that has many benefits, but data querying may slow down due to latency and HTTP overhead, especially for small blobs. The goal of ReductStore is to be suitable for data of any size, and since version 1.5.0, the database can batch multiple records in one HTTP request. This can increase the speed of downloading data by up to 80 times, depending on the size of the records.
If you’re interested in details, you can read about the GET /api/v1/b/:bucket/:entry/batch endpoint here. However, if you use one of our client SDKs, you just need to update to the latest version without making any changes to your code.
Sometimes we don’t need the content of your blob records, but only meta information like size, labels or timestamp. For this case, ReductStore provides HEAD versions of endpoints to read and query records without HTTP body.
This is an example, how to use it in python:
bucket = await reduct_client.get_bucket("test")
async for rec in bucket.query("data", head=True):
count += rec.size
Traditionally, we have aligned our official SDKs for Python, C++, and JavaScript with the latest API so that you can use the latest features.
I hope you find this release useful. If you have any questions or feedback, don’t hesitate to reach out in Discord or by opening a discussion on GitHub.
Thanks for using ReductStore!
#NewsReductStore vs. MinIO & InfluxDB on LTE Network: Who Really Wins the Speed Race?
#Comparison #IotReductStore 1.6.0 has been released with new license and client SDK for Rust
#NewsHow to Choose the Right MQTT Data Storage for Your Next Project
#Advice #DatabaseReductStore v1.5.0 has been released
#NewsTutorials (15) Computer-vision (3) Sdks (11) News (19) Cli (5) Iot (3) Comparisons (1) Edge-computing (1) Advice (1) Database (1) Comparison (1)