Open sricc opened 10 years ago
I work on this occasionally in the background. There were some great contributions recently by @martinhpedersen. We have an innovation week planned shortly here at VoltDB. Sometimes this kind of stuff gets picked up then.
What are your thoughts exactly?
Hey Ryan,
Just doing the Go vs. Node.js comparisons here at Yellowhammer and wanted to see what the plans to develop and maintain this driver for production use would be. I know that this driver was written for fun, but it would be great to have something that we could put to the test to see if the Go/VoltDB combination is a viable option for production applications.
Anyway, was just curious as to the plans for the driver.
Thanks and hope things are going well.
I think VoltDB and Go are a great combination. Would be happy to support a production use case if one were to appear. I've also considered building a database/sql implementation (without client side commit control).
Any thoughts on that approach?
On Thu, Feb 20, 2014 at 11:06 AM, Steve Ricciardelli < notifications@github.com> wrote:
Hey Ryan,
Just doing the Go vs. Node.js comparisons here at Yellowhammer and wanted to see what the plans to develop and maintain this driver for production use would be. I know that this driver was written for fun, but it would be great to have something that we could put to the test to see if the Go/VoltDB combination is a viable option for production applications.
Anyway, was just curious as to the plans for the driver.
Thanks and hope things are going well.
— Reply to this email directly or view it on GitHubhttps://github.com/rbetts/voltdbgo/issues/5#issuecomment-35637169 .
Hey we're going to put some thoughts together and shoot you an email shortly about some of this as well as just some general feedback overall.
Hi guys,
I have been working on a system at work that I've implemented in go with VoltDB, using voltdbgo. It's almost ready for testing, and so far we've been really happy with the combination. The production features' missing from voltdbgo is not a show stopper for us, but it would be really nice to have as a bonus. The goal is to have the system deployed this summer.
We've tried out some other combinations as well, but landed on golang-voltdb. The major benefits we see are efficiency combined with ease of programming in a concurrent environment. The pprof tooling combined with VoltDB's studio makes tuning performance easy.
Although I am very happy with the api of voltdbgo, a database/sql implementation does sound like an idea worth discussing, if only for the benefit of easy transition from other databases.
Any progress on this ?
No. This driver continues to languish without a loving owner. On Mon, Feb 8, 2016 at 13:02 thomasmodeneis notifications@github.com wrote:
Any progress on this ?
— Reply to this email directly or view it on GitHub https://github.com/rbetts/voltdbgo/issues/5#issuecomment-181440501.
Just wondering if there are any plans to make this production ready?
Specifically about:
The client doesn't timeout network reads or writes. The client doesn't reconnect closed sockets. The client doesn't provide a high level interface to connect to multiple nodes of a VoltDB database.
I'm new to Go so not in any place to contribute... yet.
Thanks.