ParadeDB developer here. BM25 FTS is becoming available on more cloud platforms, but ParadeDB is much more than that now. We'll have blog posts over the next few months detailing our work on aggregates, JOINs, filters, etc.
If you fork and modify it for use in a commercial backend (not a hosted db service), does the AGPL-3.0 license means you have to share the source of the forked repo or also of the project it is used in? On a related note, have you changed your stance on accepting issues and pull requests like some orgs?
We have many community contributors (150 and counting) who submit PRs and many users who open issues. We love them!
We're well aware that our external contributors use AI (we do too!), and we fiercely guard our product against AI slop. We ask that external contributors understand the changes they are making, and we frequently close PRs unmerged if they look like slop.
As for the AGPL question, our primary goal with this license is to protect ourselves from hyperscalers and avoid fragmenting the community. You can read more about it here: https://news.ycombinator.com/item?id=41227172
Just a giant hetzner bare metal we’ve been on for years before they jacked up the prices - thank goodness. Avg record is maybe 1-2k words. Search is very fast, but it’s an internal product and so we’re not dealing with a large user population. Anyway parade all the way. You get a proper relational database but also proper fts without having to deal with elastic etc. Just a dream, so glad they came along.
11 comments
[ 0.21 ms ] story [ 39.6 ms ] threadWe're well aware that our external contributors use AI (we do too!), and we fiercely guard our product against AI slop. We ask that external contributors understand the changes they are making, and we frequently close PRs unmerged if they look like slop.