Was this page helpful?
ScyllaDB Java Driver is available under the Apache v2 License. ScyllaDB Java Driver is a fork of DataStax Java Driver. See Copyright here.
Caution
You're viewing documentation for a previous version of Scylla Java Driver. Switch to the latest stable version.
Client routes (private networking)¶
Quick overview¶
Client routes are not available in driver 4.18.x. They were first released in 4.19.0.7.
upgrade to 4.19.0.7 or later to connect through a cloud private endpoint that publishes per-node routes; the feature also needs ScyllaDB Enterprise 2026.1 or later.
see the client routes documentation of the latest driver.
Client routes are how driver 4.19.0.7 and later connects through a private service connection:
AWS PrivateLink (PL), Azure Private Link, or GCP Private Service Connect (PSC).
Those are the provider services in front of the cluster, not names of a driver feature. After the
table it reads, the feature itself is also written as client_routes or clientroutes.
With client routes, the cluster publishes a per-node endpoint mapping in system.client_routes,
and the driver connects to each node through the hostname it finds there instead of through the
address the node broadcasts. 4.18.x neither reads that table nor handles the CLIENT_ROUTES_CHANGE
events that keep the mapping current.
A custom address translator is not a
substitute: it maps one address to another, while client routes key each node on its host_id and
follow the cluster as the mapping changes. An address translator remains the right tool for a proxy
in front of the cluster – one hostname for every node, or EC2 multi-region – provided each node
translates to its own address and port.