Why this matters
- VaultCommerce search index updates from
vaultcommerce.cdc.postgres.products— no dual-write from order API. - CDC captures INSERT/UPDATE/DELETE with before/after payloads.
- Postgres logical replication slot prevents WAL bloat if consumer stalls.
- Foundation for event-driven microservices without polling.
Postgres WALVaultCommerce OLTP
CDC topic
Search indexer
Postgres connector setup
Debezium creates publication and replication slot on vaultcommerce database. plugin.name=pgoutput. Events land on vaultcommerce.cdc.postgres.public.products with envelope containing op, before, after. VaultCommerce Elasticsearch sink consumes CDC topic.
Key points
- CDC (change data capture) — streaming DB mutations from WAL
- Replication slot — Postgres holds WAL until Debezium acknowledges
- Debezium envelope — op code (c/u/d/r), source metadata, payload
- Snapshot mode — initial bulk read (initial, never, when_needed)
- Outbox pattern — alternative when CDC of application table is insufficient
The rest of this guide is part of Pro
Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.
Still to come · 2 sections
- Operational concerns
- VaultCommerce rollout checklist
Test yourself
Answer these before moving on — recall is what makes it stick.