We’re using PostgreSQL for many years for our backend applications. It serves hundreds of queries a second, is rock solid and has any feature one can possibly think of (which is not always a good thing, I must add).
However, it also can get complex and when the data volume grows, it sometimes can become slow. Because it has so many features and configuration options, it’s hard to “master it” without diving really deep into the underlying architecture.
Since we also use Xojo for some auxiliary apps, I noticed the Valentina product line a while ago, but I always discarded it as ancient and targeted more toward fat client Desktop apps with strong reporting needs.
So yesterday I evaluated Valentina server and imported a few very big tables into it. I was suprised to see that VServer was faster than PostgreSQL in almost any respect. I added a “IndexByWords” option to one of the tables with roughly 10 million records (a logging table) and did some fulltext searches. It can handle any query below 100ms, no matter what I throw at it. There are some nice optimization features (like the zero-space RecID) and true 1-bit booleans. Also, “links”, which are kind of a replacement for traditional Foreign Keys, make working with it a breeze. It’s almost zero config and has a built-in REST API, and recently added DuckDB as an engine.
I’m trying to contain my excitement a bit and wanted to ask if anyone has real productions experience with Valentina, preferably in a server environment with 50-100 concurrent connections and a high query volume (i.e. serving a web backend). Any insights appreciated!