Service - Sell Offer Manager: Difference between revisions

From Izara Wiki
Jump to navigation Jump to search
Line 33: Line 33:
</syntaxhighlight>
</syntaxhighlight>


== TranslateIdsRequest ==
== TranslateIdsMain ==


Stores a record for any unique translateId request
Stores a record for any unique translateId process


<syntaxhighlight lang="JavaScript">
<syntaxhighlight lang="JavaScript">
{
{
translateIdsRequestId: xxx // fromType + '_' + fromResultId + '_' + toType
translateIdsMainId: xxx // fromType + '_' + fromResultId + '_' + toType
fromType
fromType
fromResultId
fromResultId
Line 45: Line 45:
toType
toType
status: // "processing"|"complete"
status: // "processing"|"complete"
requests: [..] // array of request objects waiting a reply when this request is complete
}
}
</syntaxhighlight>
</syntaxhighlight>
Line 51: Line 50:
* partition key: translateIdsRequestId
* partition key: translateIdsRequestId
* sort key: {none}
* sort key: {none}
== TranslateIdsRequests ==
Stores a record for each translateId request, only when the TranslateIdsMain is not yet complete, so once complete code knows what messages to send out.
<syntaxhighlight lang="JavaScript">
{
translateIdsMainId
translateIdRequestId: xxx // toResultId + '_' + toResultTable + '_' + hash(additionalData)
toResultId
toResultTable
additionalData
}
</syntaxhighlight>
* partition key: translateIdsMainId
* sort key: translateIdsRequestId


= Working documents =
= Working documents =

Revision as of 13:57, 4 July 2021

Overview

Each sell offer is handled by a Service - Sell Offer (handlers) service.

The Sell Offer Manager service handles shared orchestration of the Sell Offer Handler services.

Repository

https://bitbucket.org/izara-market-products/izara-market-products-sell-offer-manager/src/master/

DynamoDB tables

Standard Config Table Per Service

Configuration tags

{
	configKey: "ProductsGraphServiceName"
	configTag: "ProductsGraphServiceName"
	configValue: xxx // eg: "ProductsGraph"
}
{
	configKey: "SellOfferService"
	configTag: xxx // sellOfferServiceNameTag, eg: "SellOfferStandard", this is what is saved in each catalog record
	configValue: {
		serviceName: xxx // eg: "SellOfferStandard", this is the actual deployed service name}
	}
}

TranslateIdsMain

Stores a record for any unique translateId process

{
	translateIdsMainId: xxx // fromType + '_' + fromResultId + '_' + toType
	fromType
	fromResultId
	fromResultTable
	toType
	status: // "processing"|"complete"
}
  • partition key: translateIdsRequestId
  • sort key: {none}

TranslateIdsRequests

Stores a record for each translateId request, only when the TranslateIdsMain is not yet complete, so once complete code knows what messages to send out.

{
	translateIdsMainId
	translateIdRequestId: xxx // toResultId + '_' + toResultTable + '_' + hash(additionalData)
	toResultId
	toResultTable
	additionalData
}
  • partition key: translateIdsMainId
  • sort key: translateIdsRequestId

Working documents

Sell Offer Manager