You may understand what Motive Commerce Search is, but still want to know more about how it comes to be it.
This page provides an overview of the architecture of Motive Commerce Search and its components, working as the starting point for you to understand the technical behaviour that supports its capabilities.
Motive Commerce Search aims to provide an accurate search mechanism to help people find what they’re looking for with the joy of discovering things they didn’t know they wanted.
To provide this search tool to make shopping fun from every device, Motive Commerce Search connects to shop builders through the use of plugins.
Plugins enable communication between shop builders and Motive Commerce Search, allowing them to gather the necessary information, index it and perform the necessary steps to display the most relevant results. The adapter for PrestaShop transforms the information of your online shop to Motive Commerce Search's format, allowing the feed to facilitate the integration with it.
The plugin is required to adapt the information retrieved from PrestaShop to Motive Commerce Search’s schema. This means that, regardless of the structure of your feed, your information is correctly mapped, with both sides accepting the same data format.
Once the plugin is set up, this connection relies on different services to carry out the indexing, searching and protection provided by Motive Commerce Search. The different services interact between themselves to provide a secure and complete searching tool that results in a seamless shopping and browsing experience.
This section provides a detailed explanation of the services that work together to make Motive Commerce Search work and how they interact between them.
The Motive Service works as the orchestrator, being the one that nurtures the API for different components, such as the Dashboard, to interact with it. The Motive Service allows Motive Commerce Search users to sign up, configure, or communicate with Motive Commerce Search.
The Motive Service will also be in charge of allowing front-end components, such as the Dashboard, to connect to the Motive API.
The Index Service, closely related to the Search Service, is the entry point for the schemas and feeds. This means that existing feeds and their associated schemas are digested by this service to index them in the best possible way. By indexing schemas, Motive Commerce Search achieves a sorting of results that is relevant for its users.
The Index Service carries out this indexing automatically. In the future, it is expected to evolve into an Index API that would be in charge of receiving the petitions, and pull the workers so that data can be managed more efficiently when the product scales, allowing the management of petitions in the queue to execute them in the best and most efficient possible way.
The Index Service thus provides an inventory of data that the Search Service can retrieve to offer the most relevant results. This service is in charge of sending all that data to ElasticSearch: a distributed, free and open search and analytics engine for all types of data.
This enables the Search Service to recognise a petition, search the corresponding results in ElasticSearch, build them in a user-facing way and return them to the front-end, in this case, MotiveX.
On top of all the aforementioned services, there is a layer in charge of keeping the different components and their relationships safe: the Security Service. This service is the one handling authentication and authorisation for the incoming and outgoing requests.
The different back-end and front-end components are checked against the security service to make sure they have working permissions to perform those actions, then perform an audit on these.
Now that you know the basics about how is motive structured in technical terms, why not expand that information with the following pages: