You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please don’t interpret this question as anything other than constructive as I’m working to understand the current Go-based client library space for Apache Cassandra.
I see the last commit to this popular library was nine months ago as of this post. Granted, currently, the latest version of Cassandra is 4.1.x with 5.x beta pending and this library does support Cassandra 4.1.x.
The reason for my inquiry is to understand why the last commit was nine months ago. I completely understand if the client is stable in relation to Cassandra’s API surface but it seems the accrual technical risk related to potential CVEs and technical debt related to the supply chain would warrant more recent updates.
Again, please don’t interpret this as anything other than constructive. We have quite a few services written in Go and are considering Cassandra for an area of our system that would benefit from non-relational columnar-orientated durable storage and are looking to find the “best” Go client to use.
Your help, insights, and guidance are greatly appreciated.
The text was updated successfully, but these errors were encountered:
mprimeaux
changed the title
QUESTION: Status of this project…
QUESTION: Status of this Project
May 10, 2024
Hi all.
Please don’t interpret this question as anything other than constructive as I’m working to understand the current Go-based client library space for Apache Cassandra.
I see the last commit to this popular library was nine months ago as of this post. Granted, currently, the latest version of Cassandra is 4.1.x with
5.x
beta pending and this library does support Cassandra 4.1.x.The reason for my inquiry is to understand why the last commit was nine months ago. I completely understand if the client is stable in relation to Cassandra’s API surface but it seems the accrual technical risk related to potential CVEs and technical debt related to the supply chain would warrant more recent updates.
Again, please don’t interpret this as anything other than constructive. We have quite a few services written in Go and are considering Cassandra for an area of our system that would benefit from non-relational columnar-orientated durable storage and are looking to find the “best” Go client to use.
Your help, insights, and guidance are greatly appreciated.
The text was updated successfully, but these errors were encountered: