Service - User Resource Use - Revision history

Seagame: /* UserTransactionRecord */

2023-02-03T07:37:43Z

UserTransactionRecord

← Older revision		Revision as of 07:37, 3 February 2023
Line 54:		Line 54:
	<syntaxhighlight lang="JavaScript">		<syntaxhighlight lang="JavaScript">
	{		{
			userId: xxx
			firstTransactionTime: xxx
	partitionId: xxx		partitionId: xxx
	~~userIdFirstTransactionTime: xxx~~
	}		}
	</syntaxhighlight>		</syntaxhighlight>

	* partition key: ~~partitionId~~		* partition key: userId
	* sort key~~: {userId}_{firstTransactionTime}~~		* no sort key
	* partitionId: maybe a fixed range of partition keys, eg 10, that breaks up records a little		* partitionId: maybe a fixed range of partition keys, eg 10, that breaks up records a little
	* try to generate partitionId somehow from userId in consistent way so standard partitionId for a single user, otherwise querying existing record for a user cannot be done		* try to generate partitionId somehow from userId in consistent way so standard partitionId for a single user, otherwise querying existing record for a user cannot be done
	* firstTransactionTime: useTime timestamp for the earliest resource use that has not had a transaction created yet		* firstTransactionTime: useTime timestamp for the earliest resource use that has not had a transaction created yet
	* we will be querying based on firstTransactionTime being older than transaction period, partition key is not really needed		* we will be querying based on firstTransactionTime being older than transaction period, partition key is not really needed
			* have GSI:
			** partition key: partitionId
			** sort key: firstTransactionTime
			** project: userId
			** used to find which users need to process transactions, eventual consistency is ok

	= Reporting use in services =		= Reporting use in services =

Seagame: /* UserTransactionRecord */

2023-02-02T09:10:45Z

UserTransactionRecord

← Older revision		Revision as of 09:10, 2 February 2023
Line 55:		Line 55:
	{		{
	partitionId: xxx		partitionId: xxx
	~~firstTransactionTime: xxx~~		userIdFirstTransactionTime: xxx
	~~userId~~: xxx
	}		}
	</syntaxhighlight>		</syntaxhighlight>

	* partition key: partitionId		* partition key: partitionId
	* sort key: firstTransactionTime		* sort key: {userId}_{firstTransactionTime}
	* partitionId: maybe a fixed range of partition keys, eg 10, that breaks up records a little		* partitionId: maybe a fixed range of partition keys, eg 10, that breaks up records a little
	* try to generate partitionId somehow from userId in consistent way so standard partitionId for a single user, otherwise querying existing record for a user cannot be done		* try to generate partitionId somehow from userId in consistent way so standard partitionId for a single user, otherwise querying existing record for a user cannot be done

Seagame: /* ResourceUse */

2023-01-19T07:19:43Z

ResourceUse

← Older revision		Revision as of 07:19, 19 January 2023
Line 38:		Line 38:
	useTime: xxx		useTime: xxx
	details: xxx		details: xxx
			usedUnits: xxx
	}		}
	</syntaxhighlight>		</syntaxhighlight>
Line 47:		Line 48:
	* details: an object with additional information about the resource use, eg what Lambda function, query, etc..		* details: an object with additional information about the resource use, eg what Lambda function, query, etc..
	* resourceTag: Lambda/Dynamo/Neo4j/etc..		* resourceTag: Lambda/Dynamo/Neo4j/etc..
			* usedUnits: Quantity of used per resourceTag

	== UserTransactionRecord ==		== UserTransactionRecord ==

Sven the Barbarian at 20:11, 18 January 2023

2023-01-18T20:11:15Z

@@ Line 18: / Line 18: @@
 	configTag: "UserAccountBalanceServiceName"
 	configValue: xxx // eg: "AccBalance"
+}
 </syntaxhighlight>
@@ Line 38: / Line 48: @@
 * resourceTag: Lambda/Dynamo/Neo4j/etc..
-== .. some way of recording resourceUse need to add to Account Balance... ==
+== UserTransactionRecord ==
 = Working documents =

Sven the Barbarian: Created page with "= Overview = Records resource use allocated to each user, this can be used to bill users according to their resource use, eg after free limits have been exceeded. = Repository = https://bitbucket.org/izara-core-user-accounts/izara-core-user-accounts-user-resource-use = DynamoDB tables = == Standard Config Table Per Service == === Configuration tags === { configKey: "UserAccountBalanceServiceName" configTag: "UserAccountBal..."

2023-01-18T13:38:13Z

Created page with "= Overview = Records resource use allocated to each user, this can be used to bill users according to their resource use, eg after free limits have been exceeded. = Repository = https://bitbucket.org/izara-core-user-accounts/izara-core-user-accounts-user-resource-use = DynamoDB tables = == Standard Config Table Per Service == === Configuration tags === <syntaxhighlight lang="JavaScript"> { configKey: "UserAccountBalanceServiceName" configTag: "UserAccountBal..."

New page

= Overview =

Records resource use allocated to each user, this can be used to bill users according to their resource use, eg after free limits have been exceeded.

= Repository =

https://bitbucket.org/izara-core-user-accounts/izara-core-user-accounts-user-resource-use

= DynamoDB tables =

== [[Standard Config Table Per Service]] ==

=== Configuration tags ===

<syntaxhighlight lang="JavaScript">
{
configKey: "UserAccountBalanceServiceName"
configTag: "UserAccountBalanceServiceName"
configValue: xxx // eg: "AccBalance"
}
</syntaxhighlight>

== ResourceUse ==

<syntaxhighlight lang="JavaScript">
{
userIdResource: xxx
useTime: xxx
details: xxx
}
</syntaxhighlight>

* partition key: userIdResource
* sort key: useTime
* userIdResource: userId + "_" + "resourceTag"
* useTime: {timestamp of use}_{uniqueRequestId}, add uniqueRequestId to ensure each record is unique
* details: an object with additional information about the resource use, eg what Lambda function, query, etc..
* resourceTag: Lambda/Dynamo/Neo4j/etc..

== .. some way of recording resourceUse need to add to Account Balance... ==

= Working documents =

[[:Category:Working_documents - User Resource Use|User Resource Use]]

[[Category:Backend services| User Resource Use]]