AWS Java 2.x SDK (sync vs async) Client Documentation

### Describe the issue

The documenation [here](https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/http-configuration.html) seems very confusing.

The AWS Java 2.x SDK offers many different http client alternatives. Two of which are the:

- Apache-based sync HTTP client
- AWS CRT-based async HTTP client

To help me understand the difference between the Sync and Async, I was trying to understand the differences described in the AWS documentation, as linked above.

When browsing their recommendations as to which to use, I found the following very peculiar:

> The Apache-based sync HTTP client is recommended for "low latency over high throughput", while the AWS CRT-based async HTTP client is recommended for "high throughput over low latency".

How on earth could the Apache-based sync HTTP client have a lower latency than one of the Async HTTP clients? I would expect the latency to be based on network latency and for that it's completely irrelevant which client (whether sync or async) you use.

Also, how could an Async client have a higher throughput than a sync HTTP client, that also doesn't make sense to me? I would expect the opposite because the sync client will busy wait until the response is available, while the async will go run off do something else in the meantime, and therefore might not be ready to handle the response right when it arrives.

I've also asked this [on stackoverflow](https://stackoverflow.com/questions/77280280/understanding-aws-sdk-java-2-x-async-vs-sync-http-clients), and I haven't any responses to my question yet.

### Links

https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/http-configuration.html

Comienza con la página enlazada de configuración HTTP de AWS SDK Java y revisa la redacción en torno a los clientes síncronos basados en Apache y los clientes asíncronos basados en AWS CRT. Compara las recomendaciones sobre latencia y rendimiento con las preguntas del issue; el trabajo estará terminado cuando la documentación explique claramente qué significan esas recomendaciones y por qué difieren las opciones de cliente.

Escrito por el modelo de indexación a partir del texto del issue.