Uses DynamoDB Batching API to Load and Save Record Metadata

Type of change

• Bug Fix
• Feature

Please provide link to gitlab issue or ADR(Architecture Decision Record)

Does this introduce a change in the core logic?

• [NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• GCP
• IBM

Does this introduce a breaking change?

• [NO]

What is the current behavior?

Record Metadata is loaded sequentially, with one record metadata saved/loaded per DynamoDB request.

What is the new/expected behavior?

Record Metadata is loaded in parallel, each batch is performed in parallel when loading.

Have you added/updated Unit Tests and Integration Tests?

Any other useful information