# vitess を Homebrew, Nix でインストール vitess のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。 ## インストール ```sh sudo av install brew:vitess ``` 追加のインストールコマンド: ### macOS - Homebrew (100%): ```sh brew install vitess ``` 証拠: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#vitess ``` 証拠: nixpkgs package indexes: pkgs/by-name/vi/vitess/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## パッケージ情報 - **パッケージキー:** brew:vitess - **パッケージマネージャ:** Homebrew - **バージョン:** 24.0.2 - **ソース概要:** Database clustering system for horizontal scaling of MySQL - **ホームページ:** - **リポジトリ:** - **最終更新:** 2026-07-26T00:30:33+02:00 - **生成日時:** 2026-08-03T19:37:03+00:00 ## 実行可能ファイル - docgen (エイリアス) - mysqlctl (エイリアス) - mysqlctld (エイリアス) - rulesctl (エイリアス) - topo2topo (エイリアス) - vtaclcheck (エイリアス) - vtadmin (エイリアス) - vtbackup (エイリアス) - vtbench (エイリアス) - vtclient (エイリアス) - vtcombo (エイリアス) - vtctl (エイリアス) - vtctlclient (エイリアス) - vtctld (エイリアス) - vtctldclient (エイリアス) - vtexplain (エイリアス) - vtgate (エイリアス) - vtgateclienttest (エイリアス) - vtorc (エイリアス) - vttablet (エイリアス) - vttestserver (エイリアス) - vttlstest (エイリアス) - zkctl (エイリアス) - zkctld (エイリアス) ## インストール挙動 - Bottle: 利用不可 ## バージョンと鮮度 - ページ生成日: 2026-08-03 - マネージャ版: 24.0.2 ## プロジェクトの歴史と使われ方 Vitess is an open-source database clustering system for horizontally scaling MySQL. It sits between applications and MySQL, routes queries through VTGate, manages tablets through VTTablet, and lets applications continue using MySQL-compatible clients while data is split across shards. Its historical importance comes from being a production-born database infrastructure project: it started inside YouTube, became a CNCF project, and is used as a way to move large MySQL estates toward cloud-native operations without rewriting every application around custom sharding logic. ### プロジェクトの歴史 Vitess was created at YouTube in 2010 after read replicas and application-level sharding were no longer enough to keep MySQL serving capacity ahead of traffic. The Vitess history page describes the progression from one primary database, to read replicas, to sharding, and then to the need for a reusable system around those shards. The project became public on GitHub in 2012 and later moved into a vendor-neutral governance setting. CNCF accepted Vitess as an incubation project in February 2018, and Vitess graduated in November 2019 as the eighth CNCF graduated project. Vitess 4.0 was announced at graduation time, with CNCF highlighting improved SQL query support, experimental VReplication support, and usability work aimed at making the system easier for new operators to adopt. ### 採用の歴史 CNCF's graduation announcement states that Vitess had been a core component of YouTube's database infrastructure since 2011 and had grown there to encompass tens of thousands of MySQL nodes. Vitess documentation also says it served all YouTube database traffic for more than five years. Beyond YouTube, official Vitess documentation names Slack, Square, and JD.com as production users. CNCF's Vitess project journey report describes community growth after CNCF entry, including hundreds of contributors, thousands of commits, and dozens of contributing companies during the measured period. Vitess also became commercially significant through PlanetScale, whose founders included Vitess co-creators and operators. That connection helped make Vitess familiar to developers who might never run a multi-shard MySQL fleet directly but encountered the architecture through managed database services. ### 使われ方 Operators use Vitess when a single MySQL server or manually managed replication topology is no longer enough. VTGate exposes a MySQL-compatible query endpoint, VTTablet runs alongside MySQL instances, and a topology service such as etcd, ZooKeeper, or Consul stores cluster state. Vitess is used for sharding, resharding, failover, backups, connection pooling, query protection, and large-fleet operational control. A key appeal is that applications can often continue using MySQL drivers while Vitess handles routing and cluster management below the application layer. ### パッケージ好きにとっての重要性 Vitess is the kind of package whose command list tells a story: `vtgate`, `vttablet`, `vtctl`, `vtctld`, `mysqlctl`, and related tools expose the moving parts of a distributed database control plane. For package maintainers and infrastructure developers, it represents the category of serious cloud-native database software that still preserves the MySQL protocol as an adoption bridge. ### タイムライン - 2010: Vitess was created inside YouTube to address MySQL scalability limits. - 2011: Vitess became a core component of YouTube database infrastructure. - 2012: The first public Vitess GitHub commit was made on February 24. - 2018: CNCF accepted Vitess as an incubation project in February. - 2019: CNCF announced Vitess graduation in November, alongside Vitess 4.0. - 2020: CNCF published a Vitess project journey report documenting post-CNCF community and adoption growth. ### Related projects - Vitess is related to MySQL and Percona Server because it scales and manages those databases rather than replacing their storage engine outright. - It is also related to Kubernetes, etcd, gRPC, Prometheus, ZooKeeper, and Consul through cloud-native deployment, topology, monitoring, and control-plane integrations. ### ソース - batch input current_curation.docs, current_curation.repo, and current_curation.tags - - - - ## セキュリティノート infrastructure mutation or orchestration signal. - **Geiger リスク:** orange / 中 - infrastructure mutation or orchestration signal ## 他のパッケージマネージャ記録 - Nix - vitess: normalized package name match | nixpkgs package indexes: pkgs/by-name/vi/vitess/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/vitess.yml](https://github.com/mxcl/pkgdb/blob/main/combined/vitess.yml) ## ソース - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph