Service - Catalog Manager: Difference between revisions

From Izara Wiki
Jump to navigation Jump to search
No edit summary
Line 1: Line 1:
= Overview =
= Overview =


Maintains a table of all catalogs, each catalog is handled by a [[Service - Catalog (handlers)]] and a [[Service - Category Tree (handlers)]] service, links to these are stored for efficiently handling browse requests.
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.
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.
Line 44: Line 44:
}
}
</syntaxhighlight>
</syntaxhighlight>
== Catalog ==
=== Fields ===
; catalogId
: (partition key)
; searchType
: product|variant|variantProduct
; catalogServiceNameTag
: eg: "CatalogStandard"
; categoryTreeServiceNameTag
: eg: "CategoryTreeStandard"


= Notes =
= Notes =

Revision as of 04:13, 3 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: "searchType"
	configKey: {eg: "product"|"sellOffer"|"variantProduct"}
	configValue: {
		searchResultServiceName: {eg: "searchResult"}
	}
}
{
	configTag: "catalogServiceName"
	configKey: xxx // serviceNameTag, eg: "CatalogStandard"
	configValue: {
		serviceName: xxx // eg: "CatalogStandard"
	}
}
{
	configTag: "categoryTreeServiceName"
	configKey: xxx // serviceNameTag, eg: "CategoryTreeStandard"
	configValue: {
		serviceName: xxx // eg: "CategoryTreeStandard"
	}
}

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