NPM module - izara-middleware - Revision history

Sven the Barbarian at 23:59, 8 March 2025

2025-03-08T23:59:26Z

← Older revision		Revision as of 23:59, 8 March 2025
Line 5:		Line 5:
	<!--T:2-->		<!--T:2-->
	Code that is shared by all services, including middleware code that executes at the beginning and end of each Lambda function and supporting code.		Code that is shared by all services, including middleware code that executes at the beginning and end of each Lambda function and supporting code.

			= Repository =

			https://bitbucket.org/izara-core-libraries/izara-core-library-middleware

	= Middleware = <!--T:3-->		= Middleware = <!--T:3-->

2022-10-04T04:36:50Z

2022-10-04T04:36:20Z

2022-10-04T04:36:09Z

2022-10-04T04:33:56Z

Marked this version for translation

2022-10-04T04:32:34Z

← Older revision		Revision as of 04:32, 4 October 2022
Line 1:		Line 1:
			<translate>
	= Overview =		= Overview =

Line 202:		Line 203:

	[[Category:NPM modules\| izara-middleware]]		[[Category:NPM modules\| izara-middleware]]
			</translate>

2021-05-19T00:34:31Z

← Older revision		Revision as of 00:34, 19 May 2021
Line 176:		Line 176:
	* If workflow passes back to calling services we do not pop/remove from this list, just keep adding		* If workflow passes back to calling services we do not pop/remove from this list, just keep adding
	* Maybe can remove from Dynamo __context__ field, but if we ever use Dynamo Streams will probably want to keep it		* Maybe can remove from Dynamo __context__ field, but if we ever use Dynamo Streams will probably want to keep it

			= How Debug logging is decided =

			* correlationIds has DEBUG_LOG_ENABLED setting, at the start of invocation if the request sets DEBUG_LOG_ENABLED then this is fixed, if the request does not set it then we use sampleDebugLogRate to randomize if this request is DEBUG_LOG_ENABLED
			* Each Lambda has an optional iz_logLevel set, if not set DEBUG level is used
			* if correlationIds is set to DEBUG_LOG_ENABLED this overwrites the iz_logLevel environment log level

	= Ideas =		= Ideas =

2021-05-14T03:19:49Z

SNS

← Older revision		Revision as of 03:19, 14 May 2021
Line 124:		Line 124:
	=== SNS ===		=== SNS ===

	..		Add serviceName to message attributes when publishing a message, this will be used by consumers that need to work with the service name of the sending service, eg to extract the unique topicName from the topic arn

	=== SQS ===		=== SQS ===

2021-05-03T13:18:03Z

requestServices

← Older revision		Revision as of 13:18, 3 May 2021
Line 153:		Line 153:
	=== requestServices ===		=== requestServices ===

	* probably skip this idea for now due per account AWS message filter policy limit		* probably skip this idea for now due per account AWS message filter policy limit, can maybe still use filters for high volume responses intended for specific services, if the consumer service count not large (<~5)

	* Is a list of services waiting for a response within a single process		* Is a list of services waiting for a response within a single process

2021-05-03T13:17:37Z

Special correlation ids

← Older revision		Revision as of 13:17, 3 May 2021
Line 152:		Line 152:

	=== requestServices ===		=== requestServices ===

			* probably skip this idea for now due per account AWS message filter policy limit

	* Is a list of services waiting for a response within a single process		* Is a list of services waiting for a response within a single process