Service - Catalog Manager

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 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: "CatalogService"
	configKey: xxx // catalogServiceNameTag, eg: "CatalogStandard", this is what is saved in each catalog record
	configValue: {
		serviceName: xxx // eg: "CatalogStandard", this is the actual deployed service name}
	}
}

{
	configTag: "CategoryTreeService"
	configKey: xxx // categoryTreeServiceNameTag, 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.

Working documents

Catalog Manager