However, the more specific configurations that are required to build a latency-aware DynamoDB application client are in ClientConfiguration ( JavaDocs) code implementations.įor this blog post, I build an asynchronous DynamoDB client in Java from scratch, and show how to use the ClientConfiguration implementation from the AWS SDK to define the application-specific latency requirements. For information about standard HTTP configurations, see Client Configuration.

The AWS Java SDK gives you full control over the HTTP client behavior and retry strategies. AWS Java SDK HTTP settings for DynamoDB clients I will also show two hypothetical application scenarios to illustrate the benefits of a proper configuration. In this blog post, I discuss the AWS Java SDK configuration options that are available to fine-tune the HTTP request timeout and retry behaviors for latency-aware DynamoDB clients. Depending on the AWS SDK in use, the underlying HTTP client behavior can be reconfigured from the default settings to help ensure that low-level client-server communications over HTTP honor the application’s latency requirements. Regardless of the root causes, an application that interacts with the DynamoDB service should be tuned to follow a retry strategy that helps avoid latency spikes. These spikes can occur because of retries from transient network interruptions, service-side and network-side issues, or overloaded and slow clients. When you operate such systems globally, you can occasionally experience latency spikes. Checkout and order processing in ecommerce.Massively multiplayer online games (MMOGs).Amazon DynamoDB is a NoSQL cloud database service that is designed to provide low-latency and high-throughput performance for applications and services running at scale.

Aws dynamodb client