A connector is a bridge that interacts with a specific external service or underlying data source (e.g., Databases) on behalf of user applications. A connector is either a Source or a Sink.
A source connector obtains data from an underlying data producer, and delivers it to targets after original data has been transformed into CloudEvents. It doesn't limit the way how a source retrieves data. (e.g., A source may pull data from a message queue or act as an HTTP server waiting for data sent to it).
A sink connector receives CloudEvents and does some specific business logics. (e.g., A MySQL Sink extracts useful data from CloudEvents and writes them to a MySQL database). CloudEvents - A specification for describing event data in common formats to provide interoperability across services, platforms and systems.
Add a new connector by implementing the source/sink interface using :
Connector Name | Type | Status |
---|---|---|
RocketMQ | Source | ✅ |
RocketMQ | Sink | ✅ |
ChatGPT | Source | ⬜ |
ChatGPT | Sink | ⬜ |
ClickHouse | Source | ⬜ |
ClickHouse | Sink | ⬜ |
DingDing | Source | ⬜ |
Dingtalk | Sink | ✅ |
Source | ⬜ | |
Sink | ⬜ | |
FeiShu | Source | ⬜ |
FeiShu | Sink | ✅ |
File | Source | ✅ |
File | Sink | ✅ |
Github | Source | ⬜ |
Github | Sink | ⬜ |
Http | Source | ⬜ |
Http | Sink | ⬜ |
Jdbc | Source | ⬜ |
Jdbc | Sink | ✅ |
Kafka | Source | ✅ |
Kafka | Sink | ✅ |
Knative | Source | ✅ |
Knative | Sink | ✅ |
MongoDB | Source | ✅ |
MongoDB | Sink | ✅ |
OpenFunction | Source | ✅ |
OpenFunction | Sink | ✅ |
Pravega | Source | ✅ |
Pravega | Sink | ✅ |
Promethues | Source | ✅ |
Promethues | Sink | ⬜ |
Pulsar | Source | ✅ |
Pulsar | Sink | ✅ |
Rabbitmq | Source | ✅ |
Rabbitmq | Sink | ✅ |
Redis | Source | ✅ |
Redis | Sink | ✅ |
S3File | Source | ⬜ |
S3File | Sink | ✅ |
Slack | Source | ⬜ |
Slack | Sink | ✅ |
Spring | Source | ✅ |
Spring | Sink | ✅ |
WeCom | Source | ⬜ |
WeCom | Sink | ✅ |
More connectors will be added... | Source/Sink | N/A |