Vitess integration
Your models, in Vitess.
A built-in ingestr destination: load modelled tables into Vitess.
name: out.vitess
type: ingestr
parameters:
source_connection: postgres
source_table: analytics.daily_revenue
destination: vitess$ bruin run assets/out/vitess.asset.yml
- extract · postgres analytics.daily_revenue
- load · Vitessreplace
Delivered to Vitess.
How it connects
Connected in three steps.
Vitess is a database clustering system for horizontal scaling of MySQL. ingestr supports Vitess as both a source and destination, plus change data capture through vtgate's VStream API. Vitess speaks the MySQL wire protocol, but it is selected with its own vitess:// scheme (not mysql://) so ingestr uses the Vitess-aware read, write, and CDC paths. Pointing a mysql:// URI at a Vitess server fails fast with a message te
- 01
Add a Vitess connection.
- 02
Point an ingestion asset at Vitess as its destination.
- 03
Bruin loads it on your schedule and checks every load.
Connection parameters
- user
- the vtgate user name
- password
- the password for the user
- host
- the vtgate MySQL-protocol host
- port
- the vtgate MySQL-protocol port, usually 3306
- keyspace
- the Vitess keyspace (used as the database)
The platform
Part of the Bruin platform.
Data in, ready for everything downstream: the models, the checks, the lineage and the AI layer.
01 · Move
02 · Model & govern
03 · Use
Frequently asked
Questions about Vitess.
Does Bruin have a built-in Vitess integration?
Yes. Built-in ingestr destination.
How fresh is the data?
As fresh as your schedule. Incremental loads append, merge or replace a time window, every few minutes if you like.
Do we need Bruin Cloud?
No. The Bruin CLI and ingestr run locally, in CI or in your own orchestrator. Bruin Cloud adds scheduling, lineage, alerts and the AI data analyst on top.
Ready to connect Vitess?
$100 in credits and 50 AI tasks. No credit card.
A demo walks through your own data.