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).
CloudEvents is a specification for describing event data in common formats to provide interoperability across services, platforms and systems.
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).
Add a new connector by implementing the source/sink interface using eventmesh-openconnect-java.
Connector Name | Source | Sink |
---|---|---|
RocketMQ | ✅ | ✅ |
ChatGPT | ⬜ | ⬜ |
ClickHouse | ⬜ | ⬜ |
DingTalk | ⬜ | ✅ |
⬜ | ⬜ | |
Feishu/Lark | ⬜ | ✅ |
File | ✅ | ✅ |
GitHub | ⬜ | ⬜ |
HTTP | ✅ | ⬜ |
Jdbc | ⬜ | ✅ |
Kafka | ✅ | ✅ |
Knative | ✅ | ✅ |
MongoDB | ✅ | ✅ |
OpenFunction | ✅ | ✅ |
Pravega | ✅ | ✅ |
Prometheus | ✅ | ⬜ |
Pulsar | ✅ | ✅ |
RabbitMQ | ✅ | ✅ |
Redis | ✅ | ✅ |
S3 File | ⬜ | ✅ |
Slack | ⬜ | ✅ |
Spring | ✅ | ✅ |
WeCom | ⬜ | ✅ |
⬜ | ✅ | |
More connectors will be added... | N/A | N/A |