AWS SDK VS EfficientDynamoDb

Please look into the attached document for more details, https://github.com/aws/aws-sdk-net/files/12968773/AWS_V2_accesstoken_error.docx

I've taken the source code from the GitHub page of the project. If you need the exact version, here's the commit SHA: 93a94821dc8ff7a0073b74def6549728da3b51c7.

I was able to find the github in 5 minutes. https://github.com/aws/aws-sdk-net

See: * (CLI) https://docs.aws.amazon.com/cli/latest/reference/sts/assume-role.html * (.NET SDK) https://github.com/aws/aws-sdk-net/blob/master/sdk/test/Services/SecurityToken/IntegrationTests/AssumeRole.cs

Looking at the code for the AWS SDK for .NET, I suspect the culprit of the slow initialization is the endpoints.js file. This 700+ KB megalodon JSON file is parsed every time the AWS SDK is initialized. Since this happens in the AWS Core assembly, this penalty is incurred by all AWS service clients.

I have created an issue on Github but maybe someone has met such an issue before and knows a workaround?

i googled it for you. https://github.com/aws/aws-sdk-net/issues/1649.

While SigV4 is embedded in all the AWS SDKs, it is not exposed to being used independently (e.g., API Gateway requires SigV4 signatures on requests that can't be made through the SDK).

Does this help? https://github.com/aws/aws-sdk-net/tree/master/extensions/src/AWSSDK.Extensions.NETCore.Setup

I'm not trying to criticize their implementation though, I think it is sound but perhaps a bit overwrought in this particular area. I will, on the other hand, level some criticism against the AWS implementation, yikes.

I always just do this = default; in this situation and expect the JIT to provide any potential optimizations. I didn't do the measurement myself, but the benchmarks ran against this PR showed that this = default; was ever so slightly faster. More importantly, it doesn't have the word "Unsafe" in it, so we can all sleep better at night.

AttributeValue was actually one of the first things we found as well. We ended up going a similar way to what you have described and squeezed our AttributeValue into a 9 bytes struct.

We have many ideas moving forward, like integrating composite keys, smart retry policies, supporting get-only properties, and so on. We'd love to hear the feedback from the community, so feel free to create an issue on GitHub or post your questions and suggestions here in the comments.