Your new website is growing exponentially. After a few rounds of high fives, you start scaling to meet this unexpected demand. While you can always add more front-end servers, eventually your database becomes a bottleneck, which leads you to . . .<\/p>\n
At YouTube, we went on that journey<\/a> as we scaled our MySQL deployment, which today handles the metadata for billions of daily video views and 300 hours of new video uploads per minute<\/a>. To do this, we developed the Vitess<\/a>platform, which addresses scaling challenges while hiding the associated complexity from the application layer.<\/p>\n Vitess is available as an open-source project<\/a> and runs best in a containerized environment. With Kubernetes<\/a> andGoogle Container Engine<\/a> as your container cluster manager<\/a>, it’s now a lot easier to get started. We\u2019ve created a single deployment configuration for Vitess that works on any platform that Kubernetes supports<\/a>.<\/p>\n In addition to being easy to deploy in a container cluster, Vitess also takes full advantage of the benefits offered by a container cluster manager, in particular:<\/p>\n In this environment, Vitess provides a MySQL storage layer with improved durability, scalability, and manageability.<\/p>\n We’re just getting started with this integration, but you can already run Vitess on Kubernetes<\/a> yourself. For more on Vitess, check out our website<\/a>, ask questions on our forum<\/a>, or join us on GitHub<\/a>. In particular, take a look at our overview to understand the trade-offs of Vitess versus NoSQL solutions and fully-managed MySQL solutions like Google Cloud SQL<\/a>.<\/p>\n -Posted by Anthony Yeh, Software Engineer, YouTube<\/p>\n source:\u00a0googlecloudplatform.blogspot.com<\/p>\n","protected":false},"excerpt":{"rendered":" Your new website is growing exponentially. After a few rounds of high fives, you start scaling to meet this unexpected demand. While you can always add more front-end servers, eventually your database becomes a bottleneck, which leads you to . . . Add more replicas for better read throughput and data durability Introduce sharding to\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[30],"tags":[],"class_list":["post-604","post","type-post","status-publish","format-standard","hentry","category-architecture"],"_links":{"self":[{"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/posts\/604","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/comments?post=604"}],"version-history":[{"count":1,"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/posts\/604\/revisions"}],"predecessor-version":[{"id":605,"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/posts\/604\/revisions\/605"}],"wp:attachment":[{"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/media?parent=604"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/categories?post=604"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/adriangrigoras.com\/blog\/wp-json\/wp\/v2\/tags?post=604"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n