We need to have the ability to use different DynamoDB clients and thread pools for different resource types. This would simulate bulkheads and let us tune the way we interact with different tables from the same application.
Currently a single global DynamoDBTemplate is used for every resource type. We could enhance this by providing and optional mapping of domain class to DynamoDBTemplate, and use it when creating a new SimpleDynamoDBCrudRepository. If not custom template is provided for the current domain class, we could use the default one.
We need to have the ability to use different DynamoDB clients and thread pools for different resource types. This would simulate bulkheads and let us tune the way we interact with different tables from the same application.
Currently a single global
DynamoDBTemplate
is used for every resource type. We could enhance this by providing and optional mapping of domain class toDynamoDBTemplate
, and use it when creating a newSimpleDynamoDBCrudRepository
. If not custom template is provided for the current domain class, we could use the default one.