Fix UX handbook assets (#8020)
This commit is contained in:
@@ -2,11 +2,15 @@
|
||||
|
||||
### Airbyte CDK
|
||||
|
||||
The Airbyte CDK \(Connector Development Kit\) allows you to create connectors for Sources or Destinations. If your source or destination doesn't exist, you can use the CDK to make the building process a lot easier. It generates all the tests and files you need and all you need to do is write the connector-specific code for your source or destination. We created one in Python which you can check out [here](../connector-development/cdk-python/) and the Faros AI team created a Javascript/Typescript one that you can check out [here](../connector-development/cdk-faros-js.md).
|
||||
The Airbyte CDK (Connector Development Kit) allows you to create connectors for Sources or Destinations. If your source or destination doesn't exist, you can use the CDK to make the building process a lot easier. It generates all the tests and files you need and all you need to do is write the connector-specific code for your source or destination. We created one in Python which you can check out [here](../connector-development/cdk-python/) and the Faros AI team created a Javascript/Typescript one that you can check out [here](../connector-development/cdk-faros-js.md).
|
||||
|
||||
### DAG
|
||||
|
||||
DAG stands for **Directed Acyclic Graph**. It's a term originally coined by math graph theorists that describes a tree-like process that cannot contain loops. For example, in the following diagram, you start at A and can choose B or C, which then proceed to D and E, respectively. This kind of structure is great for representing workflows and is what tools like [Airflow](https://airflow.apache.org/) use to orchestrate the execution of software based on different cases or states. 
|
||||
DAG stands for **Directed Acyclic Graph**. It's a term originally coined by math graph theorists that describes a tree-like process that cannot contain loops. For example, in the following diagram, you start at A and can choose B or C, which then proceed to D and E, respectively. This kind of structure is great for representing workflows and is what tools like [Airflow](https://airflow.apache.org) use to orchestrate the execution of software based on different cases or states.
|
||||
|
||||
 
|
||||
|
||||

|
||||
|
||||
### ETL/ELT
|
||||
|
||||
@@ -54,5 +58,4 @@ This refers to the functions that a Source or Destination must implement to succ
|
||||
This is only relevant for individuals who want to learn about or contribute to our underlying platform.
|
||||
{% endhint %}
|
||||
|
||||
[Temporal](https://temporal.io/) is a development kit that lets you create workflows, parallelize them, and handle failures/retries gracefully. We use it to reliably schedule each step of the ELT process, and a Temporal service is always deployed with each Airbyte installation.
|
||||
|
||||
[Temporal](https://temporal.io) is a development kit that lets you create workflows, parallelize them, and handle failures/retries gracefully. We use it to reliably schedule each step of the ELT process, and a Temporal service is always deployed with each Airbyte installation.
|
||||
|
||||
Reference in New Issue
Block a user