pkg.soopen package index

brew / rang 5835

Installer vitess avec Homebrew, Nix

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de vitess pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install vitess

local Homebrew formula metadata

Linux

Nixvérifié · 92%
nix profile install nixpkgs#vitess

nixpkgs package indexes · pkgs/by-name/vi/vitess/package.nix · Source: api.github.com

aperçu

Résumé du paquet

Database clustering system for horizontal scaling of MySQL

Commandes et alias

  • docgen
  • mysqlctl
  • mysqlctld
  • rulesctl
  • topo2topo
  • vtaclcheck
  • vtadmin
  • vtbackup
  • vtbench
  • vtclient
  • vtcombo
  • vtctl
  • vtctlclient
  • vtctld
  • vtctldclient
  • vtexplain
  • vtgate
  • vtgateclienttest
  • vtorc
  • vttablet
  • vttestserver
  • vttlstest
  • zkctl
  • zkctld

historique

Historique du projet et usages

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.

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

  • 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.

posture de sécurité

Niveau de risque : orange

infrastructure mutation or orchestration signal.

Classificateur de risque

risque orange · confiance moyen · infrastructure

Pourquoi

  • infrastructure mutation or orchestration signal

Signaux

  • text:cluster

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de bottle Homebrew sont disponibles pour 6 plateformes.
  • S’installe avec 1 dépendances d’exécution.
  • Les métadonnées de compilation listent 1 dépendances de compilation.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

exécutables

Exécutables installés

CommandeTypeExpositionNote
docgencliexécutable global
mysqlctlcliexécutable global
mysqlctldcliexécutable global
rulesctlcliexécutable global
topo2topocliexécutable global
vtaclcheckcliexécutable global
vtadmincliexécutable global
vtbackupcliexécutable global
vtbenchcliexécutable global
vtclientcliexécutable global
vtcombocliexécutable global
vtctlcliexécutable global
vtctlclientcliexécutable global
vtctldcliexécutable global
vtctldclientcliexécutable global
vtexplaincliexécutable global
vtgatecliexécutable global
vtgateclienttestcliexécutable global
vtorccliexécutable global
vttabletcliexécutable global
vttestservercliexécutable global
vttlstestcliexécutable global
zkctlcliexécutable global
zkctldcliexécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-08-04
version du gestionnaire24.0.2
gestionnaire mis à jour2026-07-26
données localesOK
amontà jour
dernière version détectéev24.0.2

https://github.com/vitessio/vitess

  • OKAucun avertissement de fraîcheur n'a été généré.

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:vitess
Version24.0.2
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/vitess
Page d'accueilhttps://vitess.io
Dépôthttps://github.com/vitessio/vitess
Docs amonthttps://vitess.io
LicenceApache-2.0
Archive sourcehttps://github.com/vitessio/vitess/archive/refs/tags/v24.0.2.tar.gz
Dernière mise à jour2026-07-26T00:30:33+02:00
Pulseupdated
Dépendancesetcd
Dépendances de compilationgo
Bouteilledisponible (sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
post-install Homebrewnon défini
Serviceaucun déclaré

faits du registre

Détails de la base source

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namevitess
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Nix95%

vitess

nix profile install nixpkgs#vitess
  • normalized package name match
  • Correspondance par : Vitess
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/vi/vitess/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment
  • pkg.so package database
  • pkgdb category and tag curation