Which Search Engines do you use and why? #457
Replies: 6 comments 8 replies
-
PostgreSQL, ManticoreSearch.
Fuzzy search, multi-language support, aggregation, faceting, relational operations
PostgreSQL is old/stable and extremely good for non-aggregation operations. Hosted solutions exist everywhere. ManticoreSearch kinda "happened", but is extremely fast at aggregations, although a very wonky engine with its own quirks that one needs to learn to live with. |
Beta Was this translation helpful? Give feedback.
-
|
Thx for your response. What are typical aggregation / facetings you have todo? Aggregation sure a topic which is on my list also for SEAL. ManticoreSearch was something I also look into it but did sadly not yet get it work in all cases the way I expected it to fulfill yet when I tried it. |
Beta Was this translation helpful? Give feedback.
-
|
The usual scenario is:
This is roughly e-commerce stuff with more detailed access control. |
Beta Was this translation helpful? Give feedback.
-
Typesense
it's easy to implement, has good demos on their website and provides hosted service. |
Beta Was this translation helpful? Give feedback.
-
|
Curations / Overrides looks like a nice feature of typesense thanks for your response here :) |
Beta Was this translation helpful? Give feedback.
-
|
Meilisearch. Handy for supporting typos and for its speed. |
Beta Was this translation helpful? Give feedback.
-
|
They have a really nice SDK/API very friendly for even people not very deep in the search topic. |
Beta Was this translation helpful? Give feedback.
-
|
What Search Engines do you use? Which features do you use of your Search Engines? How did you decide to use it? |
Beta Was this translation helpful? Give feedback.
-
|
Do you use replicas in Algolia for example for different sortings? |
Beta Was this translation helpful? Give feedback.
-
|
The situation hasn’t arisen, but if we had to, yes. |
Beta Was this translation helpful? Give feedback.
-
|
What Search Engines do you use? Which features do you use of your Search Engines? How did you decide to use it? |
Beta Was this translation helpful? Give feedback.
-
|
We set up a blank Sulu 3 that uses SEAL for website and admin area search. The loupe adapter works effortlessly for local development because it is configured as default after install (after figuring out, that you have to create a search index once manually). In preparation for the production deployment I wanted to switch to an adapter that could be used by multiple instances, as our app may scale vertically and a local per-pod index would be a bad design. As we already use a shared Redis for sessions and caching, Redisearch was an obvious choice. THX to @alexander-schranz Redisearch and Sulu3 are working great together since today! So the main reason for Redisearch was, that it fits seamlessly into the existing tech stack. |
Beta Was this translation helpful? Give feedback.
-
|
Thx for letting us know. That sounds great, keep in mind that you may want maybe 2 different instances of Redis for One for Cache/Sessions and One for Search. As cache/sessions mostly run on some cache policy like |
Beta Was this translation helpful? Give feedback.
-
|
Thats right, and thats even the way redis recommends¹ such cases. But currently I postpone that topic to when site size and user count reach a relevant level to hit |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
There are a lot of different search engines. In SEAL we are already supporting Elasticsearch, Opensearch, Algolia, Meilisearch, Redisearch, Typesense, Solr and Loupe.
I want to know which Search Engines do you use and why? Even if you are not using SEAL or a supported search engine of SEAL.
So my questions are:
Beta Was this translation helpful? Give feedback.
All reactions