Build for Windows from download page

[Joe Blue]

Is a windows build on the roadmap ?

On the download page there is only a docker version currently.

https://www.cockroachlabs.com/docs/install-cockroachdb.html

For many of the teams use cases, we have to support rolling out to Windows clients. Just reality.

If i can get an idea as to if its realistic that this wil happen, if if not this month, it would help my roadmaps and architecture.

Thanks in advance

Joe

[Tamir Duberstein]

Hi Joe, unfortunately it is not currently possible to build CockroachDB for Windows due to https://github.com/golang/go/issues/14985.

--
You received this message because you are subscribed to the Google Groups "CockroachDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cockroach-db...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Joe Blue]

Hey tamir,

That's a funny coincidence. I was playing around with xgo a couple of days ago.

It looks hopeful since Brad and Ian are on the issue.

From a use case perspective, I know that we are only needing windows support for desktops, not servers.
Performance is not needed. We only are doing it this way because our whole stack is postresql based and moving to cockroachdb.
On the cloud servers we of course use Linux.

So one option, which might or might not be suitable is to not use rocksdb on windows, but instead leveldb. Of course it's a potential bug regression nightmare for the team. But I did the same thing on the Bleve search project. It was designed so that boltdb, leveldb or rocks dB could be used as the underlying storage engine.
We had to run Bleve on windows, so turned on boltdb. Then for the big cloud servers used the rocks dB engine.

Just an idea, workaround.

[Dorian Hoxha]

@Joe

So you're developing while it's not production-ready yet ? Curious when you plan to put to production? (since betas are still coming out with breaking changes)

[Joe Blue]

Yep

On Tue, 31 May 2016, 23:30 Dorian Hoxha, <dorian...@gmail.com> wrote:

@Joe

So you're developing while it's not production-ready yet ? Curious when you plan to put to production? (since betas are still coming out with breaking changes)

--
You received this message because you are subscribed to a topic in the Google Groups "CockroachDB" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/cockroach-db/qmpjse5Qk9o/unsubscribe.
To unsubscribe from this group and all its topics, send an email to cockroach-db...@googlegroups.com.

[Joe Blue]

@dorian

At the moment we are using Potresql in production.

But we want to move to cockroach, and so have been playing with it.

Our middle tier is a mixture of golang and c#.

The opportunity for us, is that we can program in c#, and run tha on linux containers. But for all the IAAS stuff we can us golang.

NATS for the MS. There is a good c# driver too

Cockroach for the DB. But no c# driver yet. Looking into that a bit.

Docker for runnng it all

K8 for scaling it

H8 for the physical IIAS under it.

Stuff like Torus, etcd make it much easier also of course.

I can imagine that the c# is a bit repulsive around here :) But its a tempting opportunity for all the Microsoft shops.

On Wednesday, June 1, 2016 at 12:11:25 AM UTC+2, Joe Blue wrote:

Yep

On Tue, 31 May 2016, 23:30 Dorian Hoxha, <dorian...@gmail.com> wrote:

@Joe

So you're developing while it's not production-ready yet ? Curious when you plan to put to production? (since betas are still coming out with breaking changes)

--
You received this message because you are subscribed to a topic in the Google Groups "CockroachDB" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/cockroach-db/qmpjse5Qk9o/unsubscribe.

To unsubscribe from this group and all its topics, send an email to cockroach-db+unsubscribe@googlegroups.com.

[Dorian Hoxha]

@Joe
You're too much on the bleeding edge (is c# on linux viable yet?)
Have you looked at http://www.npgsql.org/ ?

[Joe Blue]

C# looks very close. The docker image and vscode integration turned the corner a week ago to the degree we need. No more freaky mono.
Roslyn works on OSX and you get great intellisense on your desktop.

Front end code using typescript is really nice. The intellisense and checking makes it possible to scale the front end development. There are still some loose edges but I personally find it much more productive than plain js or es2015 now.

Check it out on docker hub.

Yes I am using that driver.

Also for message queue the c# driver for NATS works well.

We are also using boltdb for shared kV stores. Was a bit pissy about the KV api of cockroach being closed :)

--

You received this message because you are subscribed to a topic in the Google Groups "CockroachDB" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/cockroach-db/qmpjse5Qk9o/unsubscribe.

To unsubscribe from this group and all its topics, send an email to cockroach-db...@googlegroups.com.

[Joe Blue]

Btw I know it's bleeding. But there is a cost / payoff ratio. Thats really multi permutation and it depends on what your project is mostly.

[Peter Mattis]

Dorian, attempting to use CockroachDB at this time is by definition bleeding edge as CockroachDB is still in beta. There are risks in doing so, but depending on the nature of Joe's project that might be perfectly appropriate. On the plus side, we're very committed to working through problems discovered by early adopters.

Joe, I'd be interested in hearing more about your use case. 

You received this message because you are subscribed to the Google Groups "CockroachDB" group.

To unsubscribe from this group and stop receiving emails from it, send an email to cockroach-db...@googlegroups.com.

[Joe Blue]

Absolutely. I am only doing blue sky due diligence. Not even at development level.

Use cases . Here goes :

kV & SQL in one dB is highly useful. At the moment we microservice / split them. Boltdb and postresql. But there is no 2 phases commit between them.

One dB that can run anywhere. It's why I was looking for a way of swapping out rocks for boltdb. Gets portability without changing all your middle tier.

Go easy on me here. This is blue sky ideas. Not production at all remember.

[Peter Mattis]

Thanks for the details, Joe.

Boltdb is an embedded KV store. Is the KV part or the embedded part important? We're aiming to make the SQL overhead of a "KV" table [1] in CockroachDB minimal.

[1] CREATE TABLE kv (k STRING PRIMARY KEY, v STRING)