Update Airbyte Protocol Docs (#13709)
This commit is contained in:
@@ -8,7 +8,7 @@ Airbyte is conceptually composed of two parts: platform and connectors.
|
||||
|
||||
The platform provides all the horizontal services required to configure and run data movement operations e.g: the UI, configuration API, job scheduling, logging, alerting, etc. and is structured as a set of microservices.
|
||||
|
||||
Connectors are independent modules which push/pull data to/from sources and destinations. Connectors are built in accordance with the [Airbyte Specification](./airbyte-specification.md), which describes the interface with which data can be moved between a source and a destination using Airbyte. Connectors are packaged as Docker images, which allows total flexibility over the technologies used to implement them.
|
||||
Connectors are independent modules which push/pull data to/from sources and destinations. Connectors are built in accordance with the [Airbyte Specification](./airbyte-protocol.md), which describes the interface with which data can be moved between a source and a destination using Airbyte. Connectors are packaged as Docker images, which allows total flexibility over the technologies used to implement them.
|
||||
|
||||
A more concrete diagram can be seen below:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user