orangechairs

Report author here. We have no bias towards nor stake in any of the three cloud providers. We partnered with all three clouds to develop the testing methodology and benchmark set. Our bias is towards providing as much information as possible to our own customers as they select their clouds and machines.

Reproduction are available on github: https://github.com/cockroachlabs/cloud-report-2021

Cockroach employee here, and I'm all in on TwinkieDB. Please start a write-in campaign.

Amazon stealing OSS products and repackaging them for profit is a behavior they are replicating over and over. Big and small projects alike are neither protected nor immune (see Mongo, Elastic, Redis,...)

To see so much of the developer community respond by placing blame on the developers is heartbreaking and at the root of the tragedy of open source. It's either: your fault for using a permissive license OR shame on you for not using a permissive license. Where is the outrage at the predatory companies cannibalizing open source?

We need to remember who the real enemy of open source is. The only company that benefits from open source shaming is Amazon.

[1] https://techcrunch.com/2019/01/09/aws-gives-open-source-the-... [2] https://news.ycombinator.com/item?id=19364534 [3] https://thenewstack.io/redis-pulls-back-on-open-source-licen...

(editor here) we fixed it. I'm so used to seeing TPC-C, that my eyes missed the "TCP".

Cockroach here: Thank you! We'll get this fixed.

(editor here) Table was corrected last night, and the text was edited per the comment above and a few keen eyes internally who also caught the confusing sentence.

Our managed service is currently provisioned by cores. We automatically add nodes to your cluster based on your usage. You can also request to add more nodes if you anticipate spikes.

We released a managed version at the end of October, with auto-scaling, geo-replication, etc. --> https://www.cockroachlabs.com/product/managed/

Not sure that there any books on it yet.

This is where organized work forces (most commonly labor unions) show their worth. It's common practice that if you are represented by a labor union, the arbitrator (private judge) is mutually agreed upon by the union and corporation, which helps mitigate massive bias in either direction. Most US companies that mandate arbitration, the employees have zero voice in selecting the arbitrator.

To echo what others have said, cashless systems -- especially in fast food chains -- are a quick way to discriminate against a whole population of the underbanked. I was in Dos Toros (burrito chain mentioned early in the article) about a month ago, and the woman in line ahead of me didn't have a card. She got so embarrassed at the register despite having ample cash to pay for her meal. I paid for her with my card, she paid me in cash, and all was fine, but no one walked away from that experience feeling good about it. It was such a unnecessary emotional stress on the woman. I feel weird returning to Dos Toros knowing this policy is creating these experiences for customers.

[cockroach employee here] Have you hit us up on Gitter or Stack Overflow to help debug and tune? We'd also love to learn more about how you're using K8s, what your setup looks like, surprises you're running into with it, etc.

[cockroach here] You can check out stories of cockroachdb production deployments here -- https://www.cockroachlabs.com/customers/

JSONB support is on our 2.0 roadmap and is actively under development.

Roadmap: https://github.com/cockroachdb/cockroach/wiki/Roadmap

Confirmed Development (I see you already reference this issue above): https://github.com/cockroachdb/cockroach/issues/2969

(cockroach here)

Baidu is using it for a new application where previously they would have used sharded MySQL (https://www.cockroachlabs.com/customers/baidu/). Their dev team is fairly active on GitHub and Gitter if you want to ping them for more details.

Heroic Labs is using it for real-time, multi-player gaming development that can support a global userbase (https://www.cockroachlabs.com/customers/heroic-labs/). I'm not sure how gitter/github/HN active they are, but they work in open source, so they're probably pretty easy to connect with.

It's true. These two guys have been working together in OSS for a long time - https://www.gimp.org/news/2015/11/22/20-years-of-gimp-releas...

[cockroachdb here] Yeah, we're experiencing some caching issues.

(cockroach labs here) No one is yet using it in production, but we're actively seeking beta clients. If you'd like to talk more, feel free to ping me: jessica @ cockroachlabs

(Cockroach Labs here) The simulations are available on Spencer's github repo here: https://github.com/spencerkimball/spencerkimball.github.io/t...

[cockroach labs here] We should clarify that the 10-node goal is our Q3 OKR. (I'll update the original post.) We're still actively developing the beta product and will be aiming for much more solid stability numbers by 1.0.

Employee here - A proper analysis from Kyle is certainly on our radar, although we'll likely wait until post-beta since its such a hefty project. We're just as eager to see how CockroachDB stacks up.

CockroachDB here. We haven't published benchmarks yet and performance work is ongoing. As this is a beta product, the current performance is not indicative of where it will eventually be.

[cockroach labs employee here] Post corrected. Good catch. =)