Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I started working on token-aware routing as a hobby project it's highly work-in-progress, but it's a start. This is one of three things that I think will make cql-proxy awesome for use with Apache Cassandra or any other CQL-based service as a general tool for handling various CQL routing related use cases:
cql-proxy
<--> backend cluster TLS (Add proxy to cluster TLS support (--cluster-ca-file
) #103)client <--> proxy
connections.With these three changes cql-proxy could be used at the edge as way to terminate traffic for Cassandra deployed on k8s or as a way to implement lightweight drivers that don't have to implement token-awareness, or connection pooling, etc. Also, having the connection to Cassandra be persistent in the proxy makes it awesome for request-based platforms e.g. PHP in Apache (the HTTP server) because connecting to the local proxy is super fast and the slow connections to C* are pooled in the proxy. This could be useful for various other scripting languages and cron-based tasks too.
It's been a joy working on
cql-proxy
and I might check in on it time to time, but please take good care of the project!