Service - Catalog Manager: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 25: | Line 25: | ||
<syntaxhighlight lang="JavaScript"> | <syntaxhighlight lang="JavaScript"> | ||
{ | { | ||
configTag: " | configTag: "SearchType" | ||
configKey: {eg: "product"|"sellOffer"|"variantProduct"} | configKey: {eg: "product"|"sellOffer"|"variantProduct"} | ||
configValue: { | configValue: { | ||
| Line 35: | Line 35: | ||
<syntaxhighlight lang="JavaScript"> | <syntaxhighlight lang="JavaScript"> | ||
{ | { | ||
configTag: " | configTag: "CatalogServiceName" | ||
configKey: xxx // serviceNameTag, eg: "CatalogStandard" | configKey: xxx // serviceNameTag, eg: "CatalogStandard", this is what is saved in each catalog record | ||
configValue: { | configValue: { | ||
serviceName: xxx // eg: "CatalogStandard" | serviceName: xxx // eg: "CatalogStandard", this is the actual deployed service name} | ||
} | } | ||
} | } | ||
| Line 45: | Line 45: | ||
<syntaxhighlight lang="JavaScript"> | <syntaxhighlight lang="JavaScript"> | ||
{ | { | ||
configTag: " | configTag: "CategoryTreeServiceName" | ||
configKey: xxx // serviceNameTag, eg: "CategoryTreeStandard" | configKey: xxx // serviceNameTag, eg: "CategoryTreeStandard", this is what is saved in each catalog record | ||
configValue: { | configValue: { | ||
serviceName: xxx // eg: "CategoryTreeStandard" | serviceName: xxx // eg: "CategoryTreeStandard", this is the actual deployed service name} | ||
} | } | ||
} | } | ||
Revision as of 02:07, 7 March 2021
Overview
Each catalog is handled by a Service - Catalog (handlers) and a Service - Category Tree (handlers) service.
Browse requests from client pass this service, the Search Result request is built and sent to Service - Search Result Main service and id/s to poll for results are sent to client.
Repository
https://bitbucket.org/stb_working/catalog-manager/src/master/
DynamoDB tables
Standard Config Table Per Service
Configuration tags
{
configTag: "CatalogGraphServiceName"
configKey: "CatalogGraphServiceName"
configValue: xxx // eg: "CatalogGraph"
}
{
configTag: "SearchType"
configKey: {eg: "product"|"sellOffer"|"variantProduct"}
configValue: {
searchResultServiceName: {eg: "searchResult"}
}
}
{
configTag: "CatalogServiceName"
configKey: xxx // serviceNameTag, eg: "CatalogStandard", this is what is saved in each catalog record
configValue: {
serviceName: xxx // eg: "CatalogStandard", this is the actual deployed service name}
}
}
{
configTag: "CategoryTreeServiceName"
configKey: xxx // serviceNameTag, eg: "CategoryTreeStandard", this is what is saved in each catalog record
configValue: {
serviceName: xxx // eg: "CategoryTreeStandard", this is the actual deployed service name}
}
}
Notes
- Client can pass in additional filters, these get combined into final Search Result request by Service - Category Tree (handlers).
- Client can overwrite default searchType, if invalid gets set to categoryTreeNode default.
- Client can add requiredData to request.
- locationTreeAreaNodeId and browseQuantity are added by the client into additionalParams, Category Tree handler adds these to the request, or set to default if invalid.