|Coveo for Sitecore Comparison||v4.1 1||v4.0 1||v3.0|
|Coveo for Sitecore Hive Framework|
|Machine Learning |
|Cloud Index |
|Coveo Usage Analytics |
2.0+ (for Coveo for Sitecore Hive)
1.0+ (for the legacy Coveo for Sitecore components)
|Release cycle||~6 weeks||~3 months|
On request only
Usage Analytics and Coveo Machine Learning
Coveo for Sitecore 4 offers the possibility to have your indexes hosted in the Coveo Cloud platform (see Understanding the Architecture of Coveo for Sitecore - Cloud). Migrating to a cloud-based index brings many advantages:
Less software: you do not need to install Coveo Enterprise Search (CES) nor the Coveo Search API. No Now, there is no need to deal with the Admin Service and RabbitMQ anymore.
- Query pipelines are now configurable by the user right from the Coveo Search Component properties (see Using a Query Pipeline).
- The on-premise architecture was modified (see Understanding the Architecture of Coveo for Sitecore - On-Premises).
- The configuration file location changed and Coveo now promotes patch file as a good development practice (see Introduction to the Coveo Configuration files).
Coveo for Sitecore Hive (4.1)
The Coveo for Sitecore Hive components allow you to create search pages by adding the components you want directly form the Sitecore Experience Editor (see Integrating Coveo for Sitecore Hive in a WebsiteUI Framework).
Instead of using a single component that strives to do everything, the search page is now split in many smaller pieces, each one representing a Coveo for Sitecore Hive component. Each component has a single responsibility and exposes displays its specific options.
You can thus move components around much more easily from the Experience Editor.
In previous Coveo for Sitecore releases, the website styling was tightly coupled to the search component view. A developer had to duplicate the search components to create their own view, mostly because of styling needs.
Leveraging Data Sources brings many benefits:
- Decouples It decouples the component settings from the component itself, making it easier to share a common set of parameter values between many components.
- Merges It merges field values through standard item inheritance. In other words, you can have a Data Source that only sets a field value and inherits values for all the other fields.
- Supports It supports local and shared Data Sources. When the Data Source item is defined as a child of the page, it is considered a local Data Source. The other alternative is to store the Data Store item elsewhere in the content tree. In such case, it is considered a shared Data Source.
As the name states, many components can reference the same Data Source item.
- Supports It supports Sitecore branches to create pre-configured search-driven pages.
The Coveo Hive components are designed with HTML caching in mind. Most of the components are "cached by Data Source," which is ideal. In order to achieve that, the rendered HTML depends solely on the Data Source parameter values. With a given set of parameters, the HTML is always the same regardless of of the current visitor, or the page it is bound to, or the current visitor.
There is one special component that makes HTML caching work for the others: the context component. Its purpose is to render all the non-cacheable information for the other components. The context HTML markup cannot be cached because it varies on many contextual factors such as the current item, the visitor, etc. Once the page is served, all the cached components can then access the context on the client-side and do their work.