Scaling and configuring search

Current version: 10.2

Search frameworks

The Sitecore Experience Platform has three search frameworks:

  • Content Search, which is used by various components primarily to search and index Sitecore items.

    Sitecore provides you with several options for configuring search results and indexing for content search.

  • xConnect Search, which is used to search and index experience data.

  • Commerce Search, which is used to search and index customers and orders.

The following table summarizes the differences between the three search frameworks:

Content Search

xConnect Search

Commerce Search

API

Sitecore Content Search API

xConnect Client API

Commerce Search Service

Providers

  • Solr

  • SolrCloud

  • Solr

  • SolrCloud

  • Solr

  • SolrCloud

Indexes

  • sitecore_core_index

  • sitecore_master_index

  • sitecore_web_index

  • sitecore_marketingdefinitions_master

  • sitecore_marketingdefinitions_web

  • sitecore_marketing_asset_index_master

  • sitecore_marketing_asset_index_web

  • sitecore_testing_index

  • sitecore_suggested_test_index

  • sitecore_fxm_master_index

  • sitecore_fxm_web_index

  • social_messages_master

  • social_messages_web

  • xdb

  • xdb_rebuild

  • Customers Scope index

  • Orders Scope index

  • Catalog Items Scope index

  • Promotions Scope index

  • Price Cards Scope index

Indexer

indexCrawler (run on the core Sitecore application)

xConnect Search Indexer (run as Windows Service or Web Job)

Commerce Minions

Many components that use the Content Search have their own API layer on top of the Content Search API. For example, the Marketing Operations API has a method for searching the sitecore_marketing_* and sitecore_marketingdefinitions_* indexes that references the Content Search API further down the stack.

Note

In Sitecore 9.0 and later, Sitecore Content Search no longer manages sitecore_list_index and sitecore_analytics_index . The xDB collection index replaces both of these indexes.

Do you have some feedback for us?

If you have suggestions for improving this article,