4 ms·
Yes, there is. We moved from ES to Vespa (vespa.ai) and never looked back. WE got better results, speed and WAY lower maintenance costs. I really don't understa
by bratao 4y ago
Yes, there is. We moved from ES to Vespa (vespa.ai) and never looked back. WE got better results, speed and WAY lower maintenance costs. I really don't understand how underrated this project is.
- murkt 4y agoHow do you deal with Vespa’s query language, YQL?
- bratao 4y agoI was also suspicious "Great, another one that wants to reinvent SQL". But in practice it works very well, to the point of I enjoying it.
- faizshah 4y agoI agree, I think if they ever decide to get it in Apache the popularity will explode. Same thing happened with flink and ignite.
- atombender 4y agoVespa seems like a great match for Elastic's text and vector search, but not for classic "OLTP"-style queries. For example, until very recently Vespa did not even have case-sensitive string field matching [1]; doing a strict equality query on a string field was not possible, and the authors did not seem to see why it would be useful. Vespa lacks a lot of this kind of basic search functionality, making it less general-purpose than Elasticsearch. It's clear that it's a very powerful search engine, though it also feels antiquated in many ways. It's very obvious that it's an ancient project that has been worked on by many different people throughout the years, with no cohesive vision or design, though it does seem like they're slowly cleaning things up. (The documentation used to be much worse, for one.) [1] https://github.com/vespa-engine/vespa/issues/10991 https://github.com/vespa-engine/vespa/issues/10991