Best practices using the Gremlin Java client with Neptune

Follow these recommendations when using the Gremlin Java client with Neptune. These best practices help you optimize performance, manage connections effectively, and avoid common pitfalls when working with the Java driver.

For information about configuring heartbeat intervals for Neptune Serverless, see Heartbeat Configuration for Neptune Serverless.

Topics

Re-use the client object across multiple threads
Create separate Gremlin Java client objects for read and write endpoints
Add multiple read replica endpoints to a Gremlin Java connection pool
Close the client to avoid the connections limit
Create a new connection after failover
Set maxInProcessPerConnection and maxSimultaneousUsagePerConnection to the same value
Send queries to the server as bytecode rather than as strings
Always completely consume the ResultSet or Iterator returned by a query
Bulk add vertices and edges in batches
Disable DNS caching in the Java Virtual Machine
Optionally, set timeouts at a per-query level
Troubleshooting java.util.concurrent.TimeoutException

Javascript is disabled or is unavailable in your browser.

To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.

Native Date and Time

Re-use the client object