Search on the Adobe AEM 6.4 | Community
Skip to main content
A
alisson_xavier
December 24, 2018
Solved

Search on the Adobe AEM 6.4

  • December 24, 2018
  • 2 replies
  • 2322 views

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.

Thanks

Alisson Xavier

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by Gaurav-Behl

    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:

    2 replies

    Gaurav-Behl
    Gaurav-BehlAccepted solution
    Level 10
    December 24, 2018

    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:

      Lokesh_Shivalingaiah
      Lokesh_Shivalingaiah
      Level 10
      December 25, 2018

      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.

        Terms & ConditionsAccessibility statement

        Loading footer...