DPP VS Reduct Storage

For me it just fails on dpp wrap file not containing a valid URL. And if I change it to https://github.com/brainboxdotcc/DPP, it fails on the repo not containing a meson.build file. And if I comment out the dependency it fails due to non-existent include/ directory. And if I comment that out, it succeeds just fine.

Sure, the D++ Discord bot library is a good example of an implementation of REST in C++. I wouldn't say it's particularly modern as it doesn't make a lot of use of modern C++ features such as constexpr, string_view and so on, but it's not too bad.

Looking quickly you'll want to use https://github.com/brainboxdotcc/DPP/blob/master/library-vcpkg/CMakeLists.txt

I've been working for many months (actually over a year now) on creating and maintaining the D++ Discord API Library (aka DPP) making it lightweight and scalable for my needs.

Out of curiousity; what does this library offer that, say, a mature library like DPP (https://github.com/brainboxdotcc/DPP) doesn't offer?

When it comes to computer vision, data storage is a critical component. You need to be able to store images for model training, as well as the results of the processing for model validation. There are a few ways to go about this, each with its own advantages and disadvantages. In this post, we’ll take a look at three different ways to store data in computer vision applications: a file system, an S3-like object storage and Reduct Storage. We’ll also discuss some of the pros and cons of each option.

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!

Reduct Storage v1.1.0 comes with a new Token API to create tokens with different permissions. This allows you to give different users or applications access to specific data or storage functions. For example, you could create a token that gives full access to all data, or one that only allows writes to a certain bucket. The Token API is simple to use and gives you a lot of flexibility in how you use Reduct Storage.

A bucket is a top-level data container of Reduct Storage. You can consider it as a folder of a file system. If you delete it, you delete all files inside the bucket. Also, it has common settings for all entries, like the quota or maximal block size.

The client has ben updated for compatibility with v1.0.0 of the storage engine's API, which is described here.

As you can see, Reduct Storage is always faster for write operations (16 times for 10 Mb blobs!!!) and a bit slower for reading when we have many small objects. You may notice that the speed decreasing for both databases when we reduce the size of chunks. This can be explained with HTTP overhead because we spend a dedicated HTTP request for each write or read operation.

You also can download binaries and run them:

Hey everyone, I just released the Reduct Storage SDK for C++ v1.0.0. Now it supports Reduct Storage v1.0.0.

We released the next major version of Reduct Storage and broke compatibility with the current client SDKs 😄. No worries, we'll fix everything soon.