FWIW, it looks like there is decent demand for something like Vitess (13790 commits) based on the number of companies that have implemented their own solutions:

• Tumblr: jetpants (1335 commits)
• Github: orchestrator (2958 commits)
• Facebook: mysql pool scanner (closed source?)
• Pinterest: bespoke (closed source, presumably)
• Uber: Schemaless (closed source?)
• Yelp: a combination of Percona and other libraries and toolkits
• Twitter: Cotton (56 commits post-Apache)
• Dropbox: Edgestore (closed source?)
• Asana: bespoke (closed source, presumably)
• Airbnb: bespoke  (closed source, presumably)
• ?: ProxySQL (2103 commits) 

On Mon, Jan 29, 2018 at 8:03 PM, Brian Grant via Lists.Cncf.Io <briangrant=google.com@lists.cncf.io> wrote:

There's even Minecraft on Vitess :-)

https://minecraftly.readme.io/v1.0/docs/what-is-minecraftly-universe

On Mon, Jan 29, 2018 at 7:28 PM, Brian Grant via Lists.Cncf.Io <briangrant=google.com@...ncf.io> wrote:

To follow up on this, with some links for external confirmation:

I think some of the confusion arose due to data being sampled at different times. The original presentation to the TOC was last April, for instance.

 

Slack presentation from 4-5 months ago. They are contributing heavily to vitess, as can be seen from the contribution stats I just sent, and even a small fraction of traffic was non-trivial.

Stichlabs has fully migrated production to Vitess: video. 

BetterCloud mentions that they use Vitess on their blog.

IMO, the production usage bar is intended primarily to assess maturity and production-worthiness, and secondarily general applicability (though 3 users isn't really enough for that). I don't think maturity and production-worthiness are concerns in this case. I think better documenting production usage via case studies is something the CNCF could help with.

As with Prometheus, Envoy, and Jaegar, Vitess was developed over the last 7 years or so for Youtube's own use. It has become more relevant to other companies with the (comparatively recent) emergence of Kubernetes. If we're looking for more user-initiated projects, Vitess is one of those.

On Mon, Jan 29, 2018 at 6:41 PM, Sugu Sougoumarane <ssougou@...> wrote:

Ah, I should have made this explicit in our slides, but here is the information to address your concerns about the graduation criteria:

The following eight companies have vitess serving production traffic:

• YouTube

• Slack

• Hubspot

• Flipkart

• Stitch Labs

• Square (Cash App)

• BetterCloud

• Quiz of Kings

Of these, engineers from the following companies have made significant contributions to the vitess code base:

• YouTube

• Slack

• Hubspot

• Flipkart

• Square (Cash App)

• StitchLabs

Additionally, the following companies have started making contributions, while in the process of evaluating:

• Booking.com

• Github

• Pinterest (new)

There are also other companies listed in the adopters page. They are evaluating vitess with the intent to mainly use it.

Finally, there are other companies, who are involved with Vitess at various levels, that wish to remain anonymous. So, we haven’t listed them here.

Please let me know if this answers your questions, or if you have others.

On 29 January 2018 at 18:08, Quinton Hoole <quinton.hoole@...> wrote:

I share Camille’s concern.

Note that the only explicit requirement in this regard w.r.t. Incubation level is as follows (from https://www.cncf.io/projects/graduation-criteria/):

• Document that it is being used successfully in production by at least three independent end users which, in the TOC’s judgement, are of adequate quality and scope.

The proposal says this about adopters:

This is an alphabetical list of known adopters of Vitess. Some have already gone into production, and others are at various stages of testing.

• YouTube
• Axon
• BetterCloud
• FlipKart
• HubSpot
• Nozzle
• Pixel Federation
• Quiz of Kings
• Slack
• Square
• Stitch Labs

Can we perhaps get some clarification about which are in production, and which are still in testing.

Sorry, this should have been brought up in the due diligence, but unfortunately got missed, by the looks of things.

Q

Quinton Hoole

Technical Vice President

America Research Center

2330 Central Expressway, Santa Clara, CA 95050

Tel: 408-330-4721   Cell: 408-320-8917   Office # E2-9

Email: quinton.hoole@...   ID#Q00403160

From: <cncf-toc@...> on behalf of Camille Fournier <skamille@...>
Reply-To: "cncf-toc@..." <cncf-toc@...>
Date: Monday, January 29, 2018 at 17:54
To: "cncf-toc@..." <cncf-toc@...>
Subject: Re: [cncf-toc] [VOTE] Vitess project proposal (incubation)

Basically, I'm concerned that there are not really actual production users who also are project committers that aren't YouTube/Google.

On Jan 29, 2018 9:53 PM, "Camille Fournier" <skamille@...> wrote:

But it is not yet in prod? Bringing it to prod sounds like not.

On Jan 29, 2018 9:51 PM, "Sugu Sougoumarane" <ssougou@...> wrote:

Just got this confirmation from Hubspot: "Definitely using. Two dedicated full timers working on bringing it to prod. Three others supporting part time, plus me. We have a handful of prod clusters at this point and are starting wider scale rollout soon."

It's likely that the slides were prepared at different times, because they were on staging for a while.

On 29 January 2018 at 17:36, Camille Fournier <skamille@...> wrote:

I'm confused, is hubspot using or evaluating this product? The different slide decks seem to disagree.

On Jan 25, 2018 12:50 PM, "Chris Aniszczyk" <caniszczyk@...g> wrote:

The TOC has decided to invite Vitess (https://github.com/youtube/vitess) as an INCUBATION level CNCF project, sponsored by Brian Grant from the TOC.

Vitess is a MySQL-compatible data orchestrator/platform. It orchestrates management of MySQL instances and has been serving all YouTube database traffic since 2011. Vitess has grown to encompass tens of thousands of MySQL nodes. It is also used by companies such as HubSpot, Slack and Square. 

The full project proposal is located here: https://github.com/cncf/toc/pull/67

Please vote (+1/0/-1) on this thread... remember that the TOC has binding votes only, but we do appreciate non-binding votes from the community as a sign of support!

--

Chris Aniszczyk (@cra) | +1-512-961-6719