pkg.soopen package index

brew / Rang 5835

vitess mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für vitess in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install vitess

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#vitess

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

Überblick

Paketzusammenfassung

Database clustering system for horizontal scaling of MySQL

Befehle und Aliase

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

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

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

Sicherheitslage

Risikostufe: orange

infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • infrastructure mutation or orchestration signal

Signale

  • text:cluster

Installationsverhalten

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
docgenExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
mysqlctlExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
mysqlctldExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
rulesctlExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
topo2topoExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vtaclcheckExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vtadminExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vtbackupExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vtbenchExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vtclientExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vtcomboExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vtctlExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vtctlclientExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vtctldExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vtctldclientExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vtexplainExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vtgateExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vtgateclienttestExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vtorcExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vttabletExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vttestserverExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
vttlstestExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
zkctlExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.
zkctldExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-08-03
Manager-Version24.0.2
Manager aktualisiert2026-07-26
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:vitess
Version24.0.2
PaketmanagerHomebrew
Homepagehttps://vitess.io
Repositoryhttps://github.com/vitessio/vitess
Zuletzt aktualisiert2026-07-26T00:30:33+02:00
Pulseupdated
Bottlenicht erfasst
Dienstkeiner deklariert

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

vitess

nix profile install nixpkgs#vitess
  • normalized package name match
  • Abgeglichen nach: 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

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

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