Pil0tXia commented on code in PR #150: URL: https://github.com/apache/eventmesh-site/pull/150#discussion_r1426926418
########## docs/design-document/03-connect/00-connectors.md: ########## @@ -2,22 +2,49 @@ ## Connector -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 connector is an image or instance 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. ## Source 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. - ## Sink 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. + ## Implements Add a new connector by implementing the source/sink interface using [eventmesh-openconnect-java](https://github.com/apache/eventmesh/tree/master/eventmesh-openconnect/eventmesh-openconnect-java). +## Technical Solution + +### Structure and process + + +### Design Detail + + +### Describe +**Worker** + Review Comment: `Worker` can be styled as a level-four heading. ########## docs/design-document/03-connect/00-connectors.md: ########## @@ -2,22 +2,49 @@ ## Connector -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 connector is an image or instance 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. ## Source 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. - ## Sink 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. + ## Implements Add a new connector by implementing the source/sink interface using [eventmesh-openconnect-java](https://github.com/apache/eventmesh/tree/master/eventmesh-openconnect/eventmesh-openconnect-java). +## Technical Solution + +### Structure and process + + Review Comment: It is better to store images in the `/static/images' path and reference them with a relative link. In Markdown, it is advisable to have a blank line between the title and the body of the text. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
