Are there any loopholes or remedies in Endeca?
We evaluate the e-commerce site as part of our academic / casestudy project. We are from India. We do not have access to any Endeca systems or any corporate systems. we only use internet for details. We have several basic questions for our research.
- Is Endeca the best or Solr?
- Are the people who have implemented Endeca satisfied? If they need to enrich search experience and UX, what should they do?
- Does Solr provide everything that Endeca provides?
- What does Endeca not provide, but Solr or other products provide?
- How to improve the Endeca system?
- What alternative capabilities can be added to the Endeca system?
- If any customer who has implemented Endeca wants to enrich their system capabilities, how can they do it? what can you suggest?
[Our research is mainly a comparison with the most preferred loopholes and software fixes. We analyzed many software products and found that Endeca is the most preferred and everyone is satisfied. We could not find any negative comments for this product. why we chose this product]
a source to share
You are asking a very broad question that will be opinion-based. I will offer my opinion.
Someone asked about Endeca on the Solr list and [I answered]. 1 His question was framed in terms of what Endeca has what Solr does not. But Solr has things that Endeca doesn't. For example, Solr has a weighted relevance scoring model (its formula), whereas Endeca is indeed sorted, which I find less desirable. In many ways, the systems have similar capabilities, each of which works slightly differently, but can usually achieve the same client goals, perhaps with different characteristics. Both are capable. However, I am looking forward to using Endeca again and staying with Solr.
a source to share
I've worked with Endeca before, but not Solr, so I can only offer one side of the discussion. Endeca is pretty good at what it does, once you get down to the system configuration management learning curve and learn how to complete the tasks (figuring out how to make this type of search work, how to combine multiple recordsets, etc.). There is a certain amount of art for building a pipeline to build an index for your specific needs, but to be honest, I worked on it for an odd search requirement, so I would suggest that it is generally a good idea to design the pipeline process correctly, with a little practice. I would say that the biggest and only real problem with Endeca I know of is the huge price tag. It is extremely expensive for a product license,and if you need professional consultants to help, you will be bleeding money. Based on the price, without even using Solr, I would venture to hire someone to learn Solr, implement it, and spend a lot of time tweaking it or buying more hardware to meet any speed requirement.
a source to share
the first comment on search rankings appears to be one of the few places where SOLR beats Endeca (except perhaps for price). I have been exposed to SOLR in a production environment and am a longtime Endeca user. My impression is that Endeca comes with tons of web interfaces and cmdline deployment tools, whereas you are on your own with SOLR. It is important for us that end users (not engineers) can manage and configure various parameters in the system. I'm sure SOLR is 100% configured in config files, so all changes will go through engineers. In Endeca, a set of parameters is user configurable. We also use the Builder product for Endeca, which allows for basic (and integrated) content management.We can change pages on the site without code clicks (just Endeca config settings, which are super lightweight). We store about 18 million records at Endeca, and there are others that are over 100mm. We get a sub-10ms response to distract individual entries and a sub-100ms response to pull out most of the navigation states (although we're not very optimized so you can achieve this much below with some effort). SOLR has another feature where you can access the navigation states with your own ID. Endeca uses an intermediate value to transition to navigation states (although an Endeca release later this year will add this feature). This is usually not that much because you usually get the navigation states from the SOLR / Endeca engine on the fly and you don't need to compute them yourself.
a source to share