Below you see a diagram of a typical solution setup. Things in Blue are hosted and controlled by Relewise while things in Green are your own Website/Webshop.
Let's explore the individual building blocks from bottom to top.
Data Entities are the stored data in Relewise
- Product Data (and their metadata) are stored in order to link search terms and related products together.
- Content Data (Blogs, Articles, etc.) are stored as well so that such data can also be searched and recommended.
- Users and User-tracking-behaviour are stored in order to make searches and recommendations personal and more relevant.
The solution is offered via an API (Application Programming Interface) using the MACH Principles, which stand for Microservices-based, API-first, Cloud-native, and Headless. These are fancy words that essentially just mean that the services are hosted in the cloud in such a manner that it can scale with your business.
The most important part here is that it is Headless, which decouples the look and feel from the service itself, meaning that you and your developers can 100% decide how the searches and recommendations are presented to the end-user. In other words, you do not need to settle for a pre-determined look and feel.
The Main API Services
- Recommendation Engine is the part that makes recommendations, for example based on what other people have purchased alongside the product that was just added to the shopping basket.
- Search Engine is the part that makes a search experience available to the user - and make it intelligent by assisting with things like spelling errors and relevance
- Admin is the administration of Products, Indexes, Triggers, and other configuration data
See how to Get Started here
My Relewise sits on top of the API, and is where you can get insights into the performance of Relewise as well as configure different areas of the service. My Relewise also contains valuable information for developers working with the implementation of Relewise.