Connectors · Current Path
Connect the systems that shape operational state.
Tapstate currently publishes MySQL and PostgreSQL as Snapshot + CDC sources, with MongoDB as the operational-state target. See exactly where each connector fits, what it requires, and what the current preview supports.
Sources
MySQL
Source · Snapshot & CDC
PostgreSQL
Source · Snapshot & CDC
Tapstate
Capture → Transform → Serve
MongoDB
Operational State Target
Published Connector Roles
Three connectors. One current path.
Each connector has a specific role in the current Tapstate preview. Roles, modes, compatibility, and preparation requirements are explicit rather than inferred from the broader connector catalog.
Current Path in Practice
Two sources. One maintained object.
The current Quickstart captures orders from MySQL and shipments from PostgreSQL, assembles them into one current order state, and keeps the resulting MongoDB document updated as either source changes.
MySQL
orders
order_id · customer_id · status
PostgreSQL
shipments
order_id · carrier · status
Tapstate · nest
Maintain current state
MongoDB
order_state
- order_id
- 10492
- status
- shipped
- carrier
- ups
Compatibility is a Contract
A connector is more than a logo.
CDC depends on what the source exposes, how it is configured, and whether the required change history remains available. A recognized system is only the beginning.
MySQL source
Change mechanism: Binary log
Before CDC
- Replication access
- binlog_format = ROW
- binlog_row_image = FULL
- Retention longer than the expected interruption window
CDC cannot resume from binlog history that has expired or been removed.
PostgreSQL source
Change mechanism: WAL · pgoutput
Before CDC
- Replication access
- wal_level = logical
- Replication slots / WAL senders
- Replica identity where required for update/delete placement
WAL and replication-slot state must remain available for the change path.
Connection passed ≠ CDC validated.
Verify a representative snapshot plus insert, update, and delete behavior before relying on a change path.
Connector ≠ Connection
Define capability once. Apply it to each environment.
A connector defines what Tapstate knows about a system. A connection applies that capability to a specific endpoint, credential set, scope, and environment.
MySQL connector
System capability
- Role
- Source
- Read modes
- Snapshot · CDC
- Contract
- Source requirements
Production
Source · CDCorders_prod
- Production endpoint
- Scoped credentials
- Scope: orders/*
Staging
Source · Snapshotorders_stage
- Staging endpoint
- Test credentials
- Scope: sample_orders/*
Same model on the target side
MongoDB connection
customer_state
Operational State Target
Destination endpoint · Write scope
Connector = capability · Connection = endpoint + credentials + scope + environment
The connector defines what the system can do. A connection defines where and how that capability is used.
Status, Without the Guesswork
Availability and maturity are different signals.
Published role in the current Tapstate product path.
The current Tapstate product and release stage.
How stable the connector guide and configuration contract are.
GA on a connector guide describes guide/configuration-contract maturity. It does not by itself mean production readiness or universal artifact availability.
What’s Next
Expand the path without blurring today’s boundary.
MySQL + PostgreSQL → Tapstate → MongoDB
Current path
Two published sources feeding one maintained operational-state target.
Kafka / Confluent
Event-path integration
Future direction. Not part of the current published connector path.
Additional enterprise sources
Under evaluation
Expanded according to operational demand, engineering validation, and connector maturity.
Roadmap items do not imply current runtime support or a committed release date.
Ready to Connect
Start with the path that is published today.
Prepare MySQL, PostgreSQL, or MongoDB with the current setup guides. Need another system? Tell us what your operational path requires.