reduct-js VS sdk-js

When we call bucket.beginWrite we create an entry in the bucket if it doesn’t exist yet. Then we write data to the entry with the current timestamp. Now our MQTT data is safe and sound in the storage, and we can access them by using the same SDK.

Traditionally, we have aligned our official SDKs for Python, C++, and JavaScript with the latest API so that you can use the latest features.

JavaScript Client SDK

You can use this feature in a Python or JavaScript application by using the Python and JavaScript client SDKs.

we are pleased to announce the release of version 1.3.0 of the ReductStore SDK for JavaScript. This version supports the new features of ReductStore v1.3, including labels and content type.

Now that you have a basic understanding of how ReductStore works, you can start using it in your projects. You can find more information about the ReductStore JavaScript SDK here.

When we call bucket.beginWrite we create an entry in the bucket if it doesn't exist yet. Then we write data to the entry with the current timestamp. Now our MQTT data is safe and sound in the storage, and we can access them by using the same SDK.

ReductStore has released v1.2.0 of its JavaScript SDK. This update includes support for ReductStore API version 1.2 with the new Client.me method, which allows you to retrieve information about your current API token and its permissions.

If you've been using the Reduct Storage client-side SDKs for Python, JavaScript or C++ to interact with your storage instances, then you'll want to upgrade to the latest version. This week, all of our SDKs were updated to support Reduct Storage v1.1.0 with Token API. With this new release, we've made some important enhancements and bug fixes that will make your development experience smoother and more productive. So make sure you upgrade today!

Python, JavaScript, or C++ SDKs

For event publishing, we're using a new API endpoint /webhook/{config_id}/trigger?sync=true|false. The endpoint checks if the data is bigger than 256kb and, if so, stores it on S3. After that, it triggers the Step Function either in the background or synchronously. This setup is great because it means consumers don't have to worry about permissions; they just need to set up our webhook client. Of course, the consumer can still use the old method of just sending an EventBridge event to trigger the webhook like before.

Our application is entirely built and designed on the same APIs we expose to our customers and technical partners via our open source SDK and public documentation.