Diarkis Match Maker
Diarkis Cloud has built-in Match Maker definitions for the client to use via HTTP REST APIs.
Diarkis Match Maker is extremely powerful. It can handle hundreds of thousands of match-making in real-time. No need for waiting for background match-making processes at all. Auto-scaling also ensures fast and reliable match-making for large-scale applications.
Rank Matching
Rank matching has three Match Maker definitions. Diarkis Match Maker searches by range, and these three definitions each have different conditions ranging from 1, 10, and 100.
Rank Matching – rank1
rank1 searches in the range of 1. It means if you are searching by “4”, rank1 finds items ONLY with “4”.
Rank Matching – rank10
rank1 searches in the range of 10. It means if you are searching by “4”, rank10 finds items between “1” and “10”.
If you search by “203”, rank10 will find items that are between “201” and “210”.
Rank Matching – rank100
rank1 searches in the range of 100. It means if you are searching by “140”, rank100 finds items between “101” and “200”. If you search by “223”, rank10 will find items that are between “201” and “300”.
Score Matching
Score matching has three Match Maker definitions exactly the same as Rank Matching.
How To Add An Item To Match Maker (Make items searchable)
In order for an item (it can be the client, room, or anything), you need to “add” the item to the Match Maker.
To have long-lasting searchable items (TTL longer than 60 seconds), you need to “add” the items repeatedly with shorter TTL (maximum of 60 seconds) until you no longer need them.
The example below uses the Score Matching range 10.
Request Body
| ID | A unique identifier to uniquely identify the item being added. |
| properties | JSON encoded searchable property: { “value”: <integer> } |
| TTL | TTL in seconds of the item being added. Maximum TTL is 60 seconds. |
How To Remove An Item From Match Maker
You may remove a specific item from Match Maker. Removing an item is expensive and it is better to rely on TTL in general.
Request Body
| ID | A unique ID of the item to be removed. |
How To Search Items Using Match Maker
The example shows how to search added items. “conditions” is matched against “properties”.
Example:
If searched with conditions { “value”: 10 }, the results will be items between “properties”: { “value”: 0 } and { “value”: 10 }
The example below uses the Score Matching range 10.
Request Body
| conditions | JSON encoded search conditions: { “value”: <integer> } |
| howMany | Maximum number of results. If omitted, it is set to be 10. |
How To Search Items In Multiple Match Maker Definitions
You may search across multiple Match Maker definitions to perform more complex searches.
Example below shows searching in score10 → score100. The idea of the example is to search with strict conditions (score10) and if enough items are not found, search in less strict conditions (score100).
The example below uses the Score Matching range of 10 and 100.
Request Body Example
| conditions | JSON encoded search conditions: { “value”: 32 } |
| howMany | 20 |