Alibaba Canal

MySQL binlog CDC server that poses as a replica and publishes row changes.

Provider
default
Category
Messaging
Properties · 3 set by this component
propertytypevaluesrequiredkind defaultthis component
deployment · component propertyenumdeployer | adapter | adminnodeployerinherited
haCoordination · component propertyenumnone | zookeepernononeinherited
managedboolean—nofalse▸ false
modeenumlog-based | trigger | pollingnolog-based▸ log-based
orderedboolean—notrue▸ true
schemaEvolutionboolean—nofalseinherited
Rules that apply · 0

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

No rule reads this kind yet. That is a gap, not a guarantee.
Use it in a design
nodes:
  - { id: "canal", component: "canal" }
Other Change data capture products · 14
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# Alibaba Canal: MySQL CDC that disguises itself as a MySQL slave, sends the dump protocol to the
# master and parses binlog events, so capture is log-based and in binlog order ("Canal wiki, Home").
# Self-hosted: canal-deployer server plus optional canal-adapter and canal-admin.
schemaVersion: "1"
type: "component"
id: "canal"
kind: "change-data-capture"
provider: "default"
docs: "https://github.com/alibaba/canal/wiki"
defaults:
  managed: false
  mode: "log-based"
  ordered: true
properties:
  deployment:
    type: "enum"
    values: ["deployer", "adapter", "admin"]
    default: "deployer"
  haCoordination:
    type: "enum"
    values: ["none", "zookeeper"]
    default: "none"

The same page as markdown, for an agent: /catalogue/components/canal.md