Thanks for the great feedback @elcritch ! It’s great to hear you are finding CubDB useful and reliable ![]()
As for me, I am running CubDB in a customer-facing product for data logging and to persist configuration. As the project creator, I was a very early adopter, so I initially had to deal with occasional issues, but all is running very smoothly since months now, on multiple devices deployed remotely.
In other words, CubDB is a version 0.x.y because a database deserves extensive testing in a variety of scenarios before being declared v1, but it’s used in production with stability requirements. It’s API won’t unexpectedly change in backwards incompatible ways, unless strictly needed and clearly communicated.
Always very valuable for me to hear users’ feedback ![]()






















