A key issue for me is API compatibility. It's nice to do simple and scalable, but you can't have both at once.
API compatibility message I can run simple for small setups and scalable for large ones. That's nice and something I strive for in software I build.
doesn't look like the case here as they don't even have an API (to be drop-in replacement for ES)
Re:We Picked AGPL
by philippemnoel on Tuesday August 13, 2024 @06:51PM
(#41240679)
We have some API-compatibility in faceted search. But yes, we are not (today) a drop-in replacement for ES. We have many migrations from ES/OpenSearch and users find that converting their code over is well worth the savings in maintenance, no-ETL and increased uptime, though.
That said, we may one day add ES API compatibility if we can :)
is there a place where I can read about what ParadeDB actually does? Surely you do more than just pre-install the extensions? Do you also develop the extensions yourself? Do you support RAG? The last question may not make sense as I am new to this space.
Re:We Picked AGPL
by philippemnoel on Tuesday August 13, 2024 @06:53PM
(#41240700)
Blog author here. That's fair! We'll add horizontal scaling eventually, but for now, our customers (including some large brands!) have not needed it. Turns you single nodes are remarkably powerful nowadays
Without horizontal scaling it's more like a hosted/queryable Lucene.