Expand my Community achievements bar.

SOLVED

Search on the Adobe AEM 6.4

Avatar

Level 1

Hi guys,

It's my first time that I'm developing search on the AEM.

I'm need to create the website search. Something like that picture bellow.

Anyone give me a suggestion if is it better use SQL 2(lucene) or use SOLR?

If anyone has an site explain anything about the search in AEM 6.4 it will be welcome.

1653399_pastedImage_0.png

Thanks

Alisson Xavier

1 Accepted Solution

Avatar

Correct answer by
Level 10

There are a lot of aspects attached to this kind of comprehensive end-to-end search design & solution. There are a lot of threads in this forum to help you with a lot of questions and you may ask other specific questions which are not answered. A few aspects to this solution are:

  • Design strategy based on specific requirements for each use case e.g. where the content is stored, how would it be fetched etc.
  • Component development strategy again based on requirements
  • Search framework
    • Lucene vs Solr vs Search n Promote vs any other solution based on requirements, source & size of content to be queried, performance strategy & SLAs, caching strategy, indexing/re-indexing strategy, etc.
  • Business rules implementation - configuration based, scheduler based, fully automated vs partial automated etc.
    • depends on requirements, locale specific, user generated content, authorized vs unauthorized content, curated content, search-results overrides etc.
  • performance for
    • queries & fetching results
    • load time of results
    • cached vs non-cached content

Couple of resources for reference:

View solution in original post

2 Replies

Avatar

Correct answer by
Level 10

There are a lot of aspects attached to this kind of comprehensive end-to-end search design & solution. There are a lot of threads in this forum to help you with a lot of questions and you may ask other specific questions which are not answered. A few aspects to this solution are:

  • Design strategy based on specific requirements for each use case e.g. where the content is stored, how would it be fetched etc.
  • Component development strategy again based on requirements
  • Search framework
    • Lucene vs Solr vs Search n Promote vs any other solution based on requirements, source & size of content to be queried, performance strategy & SLAs, caching strategy, indexing/re-indexing strategy, etc.
  • Business rules implementation - configuration based, scheduler based, fully automated vs partial automated etc.
    • depends on requirements, locale specific, user generated content, authorized vs unauthorized content, curated content, search-results overrides etc.
  • performance for
    • queries & fetching results
    • load time of results
    • cached vs non-cached content

Couple of resources for reference:

Avatar

Level 10

Hi Alisson,

As Gaurav mentioned, there are lot of aspects to decide on the search solution and it depends on the scope and objective of the search.

If its a simple search within AEM web application without lot of features like boosting, relevance etc, then you can implement that within AEM (lucene) using SQL2 queries. However if its more enterprise level search, then it would be suggested to use an external search engines like Solr, Search and promote, Elastic Search etc.