http4k-connect VS aws-sdk-java-v2

http4k-connect is a set of lightweight (zero-reflection) API libraries for connecting to popular third-party cloud services using http4k clients, along with Fake implementations for usage during local testing. It is based around the Connect pattern, which allows you to express client-side adapters in modular and composable way.

Great stack! Just out of interest , any reason you don't use Http4k connect for your AWS needs?

TBH, the official SDK dynamo client library isn't great for either. If you're looking for something lightweight, you could try http4k-connect - the dynamo client API is much nicer, does type-safety by plugging into the http4k lens system, and is zero reflection (using Moshi and generated adapters), which means you can simply cross compile to GraalVM. We're using it for native Kotlin Lambdas using the custom http4k Lambda runtime and it's 🚀🚀🚀. You can also use it backed by the OkHttp client wrapper if you want.

In this article we'll now add another dimension to our measurements : the choice of HTTP Client implementation. This is also interesting, because starting from AWS SDK for Java version 2.22 AWS added support for their own implementation of the synchronous CRT HTTP Client. The asynchronous CRT HTTP client has been generally available since February 2023. In this article we'll explore synchronous HTTP clients first and leave asynchronous ones for the next article.

The updates could be parsed from the github repo's CHANGELOG files (ex: javascript, java, python). I'm picturing an RSS feed generated for a specific language and module (ex: python s3, javascript s3, java sqs)

Meanwhile the [SDK doesn't provide samples or an API for USER_SRP_AUTH AuthFlow](https://github.com/aws/aws-sdk-java-v2/issues/2851). (I don't think that's the right choice, anyway, because if I'm right I'd have to register my user in my new app, and I don't want to do that).

Bonus: AWS SDK for Java v2 - this one I'm not sure of their reasons, but this request to add nullability annotations was filed 4.5 years ago, and there has been virtually no movement or feedback on it, so I can only speculate about their reasons for not fixing this.

If you think its a genuine bug in the API or the client somehow I think opening an issue in the github repo for the sdk might be a good place to start https://github.com/aws/aws-sdk-java-v2/issues .

Should be possible to just issue a GetObject with a range for the initial request skipping a head request. See here for caveats about how the Content Range data is returned in the response header: https://github.com/aws/aws-sdk-java-v2/issues/1209

V2 AWS SDK for Dynamo DB, SNS, and SQS

DynamoDB mapper AWS SDK v2 readme