1. 19

[cockroachdb engineering intern]

  1.  

  2. 6

    Congratulations on delivering. The Baidu test at a billion shows throughput stability has come far. What’s your longest-running, very-high-throughput cluster so far? And homogenous and mixed workloads can be counted separately there given some organizations won’t care about mixed for OLTP part. Also, have you had anyone model-check or exhaustively test the protocols for HA parts?

    1. 0

      release for software announcements. :)

      we are happy to additionally announce our series B raise of $27M

      That seems like a lot to crawl out from under…

      Also, @irfansharif please avoid dropping marketing here when you haven’t participated in our community.

      It’s tacky.

      1. 13

        I don’t see a problem with this, I was very happy to see this posted, I don’t care who posted it. We already have the upvote system to filter content.

        1. 1

          That’s cool you don’t see a problem with this. I do.

          We’ve had problems with this in the past, and once you normalize the behavior it tends to get worse and worse.

          Imagine you were at a party and a person who never talked to any of the other guests came up and started telling you about a time share–hell, assume you were even in the market for a time share.

          Would you want to keep going to parties at a place where it became known that that was a good place to get pitched on things?

          Tech culture is rotten enough with the hustle and advertising of spurious (if sometimes useful) products as it is, we need not foster it here.

          Had the post been the intern’s experience, a reflection on things learned while working at CockroachDB, a review of what makes it good compared to other databases, or whatever else, and had not been the first thing submitted by the user who has no previous history of interacting with the community here (no comments, no stories, nada), I wouldn’t have complained.

          Hell, we’ve had a lot of previous submissions about CockroachDB.

          But we’ve also had multiple people decide to drop marketing spam here.

          1. 2

            Time share? Terrible example of something with no value to readers here. Let’s do one that actually compares. So, these two guys make this thing called UNIX that delivers a never-before-seen combo of features that wow’s people. Anyone that can use it is using it but it’s proprietary with a big company that’s not acting in users’ interests or might not later. Then, some group creates a FOSS derivative of that tool called BSD. Those capabilities in high demand and that are technically interesting are now available as FOSS. They drop it on Lobsters as their first submission. Except, in this case, it’s even harder to derive as they had to invent new, hard concepts rather than a port of existing ones.

            You’d tell them to take their marketing elsewhere whereas I’d say “Holy shit, there’s a free version of something that made me say ‘Holy Shit’ before! It might even benefit a lot of admins or db fans here after bugs get shaken out.” Looking at prior submissions, quite a few were technical pieces that got significant upvotes because readers enjoyed and learned from them. There were some talking beta’s, yet another article on scaling in Go, they had some problems, etc. where I agree we don’t need it here. The votes agreed, too. Hell, you normally comment “maybe add a release tag” on FOSS project submissions with unknown significance but “no marketing” on a Spanner competitor? A little inconsistent. So, if we’re talking about marketing, I think an exception should be made for a 1.0 release of FOSS solving a hard problem with interesting internals possibly worth copying in other apps in that domain. Updates on product development, feature comparisons, and other marketing fluff of should stay on other forums as you’ve said before.

            Note: And this is coming from the guy that was Public Enemy No 1 on CochroachDB threads at HN for slamming the shit out of them on things like no stability focus early on. No bias here except in favor of rewarding hard, useful, and free tech.

            1. 1

              Again, those other submissions were by established community members, weren’t just a product roadmap, and weren’t bragging about a Series B round in their opening paragraphs.

              As for your BSD example, I wouldn’t have downvoted that since it came from an academic institution and not an intern of a tech startup shilling as their first (and heretofore only) community contribution. ;)

              1. 3

                The funding is actually extremely relevant to me because It means I have more reason to trust it won’t be abandoned. It is no secret that database companies are notorious for failure, and cockroachdb has had some problems with stability. The last thing I want to do is use something guaranteed to fail due to lack of funding.

        2. 11

          right, long time observer but first time posting. didn’t realize this would make for a bad first post but mentioned my affiliation up above.

          1. -4

            Regrettably, lurking and observing is no substitute for participation. :)

          2. 6

            I have mixed feelings about it. Spanner/F1 is possibly best DB ever invented in terms of consistency, geo, speed, and cost. Only two competitors were on my radar even attempting to replace it. Apple acqui-killed one (FoundationDB). The remaining one hitting 1.0 with a FOSS release is newsworthy to technical audience. It means it’s time to play and peer review.

            At least for DB people. Im hands off on it for now except for assessing assurance methods from the technical posts.

            Note to all: Im interested in any other projects you know with serious talent and funding trying to compete with F1 RDBMS.