Hector was developed by Ran Tavory as a high-level interface that overlays the shortcomings of Thrift.

The default is called RoundRobinBalancingPolicy and is a simple round-robin distribution algorithm.

The LeastActiveBalancingPolicy routes requests to the pools having the lowest number of active connections, ensuring a good spread of utilisation across the cluster.

[7] The ExhaustedPolicy determines how the underlying client connection pools are controlled.

Currently, three options are available:[8] As an example, an implementation of a simple distributed hashtable over Cassandra is listed.