Hello hn, I’m Alex the creator of TidesDB and over the past few months I’ve been working on putting TidesDB to work inside MariaDB through a plugin which the project is labeled TideSQL.
The project has grown quite a lot where I’d like to share it.
The plugin allows for MariaDB to optimize writes; not leave resources on the table and optionally scale infinitely. In tpc-c benchmarks the plugin shows rather great numbers comparing to MyRocks and InnoDB, you can find this analysis on the TidesDB website.
They screwed up, the source is out there, 1000s of people have a copy now. It will show up in other places where they won't be able to have it taken down
They could have prevented this by looking at the files that were about to be published.
I don’t feel that way at all. I’ve been maintaining open source storage systems for few years. I love it. Absolutely love it. I maintain TidesDB it’s a storage engine. I also have back pain but that doesn’t mean you can’t do what you love.
TidesDB is a storage engine, you use it to build databases. It's persistent and built on a log-structured-merge tree (LSM) with modern research incorporated such as
I work on https://github.com/xtdb/xtdb which is broadly Postgres-compatible with a few key SQL extensions (SQL:2011 bitemporal tables + immutability, first-class nested data, pipeline syntax, etc). Built on Arrow and the JVM but is otherwise mostly from scratch.
XTDB is perhaps not directly relevant to the topic at hand, but I am a firm believer that ML workflows can benefit from robust temporal modelling.
reply