# Data Mesh Setup

Paradime supports dbt™️ Mesh—enabling cross-project dependencies in your data mesh implementation. With Paradime, you can seamlessly integrate multiple dbt™️ projects, ensuring that various data teams can collaborate efficiently and maintain a cohesive data ecosystem.

This enhanced capability allows for streamlined data workflows, improved data quality, and robust data lineage tracking across projects.

## Key components:

* [**Cross-project references**](https://docs.paradime.io/app-help/best-practices/data-mesh-setup/configure-project-dependencies) - this is the foundational feature that enables the multi-project deployments. `{{ ref() }}`
* [**Model Groups**](https://docs.paradime.io/app-help/best-practices/data-mesh-setup/model-groups) - With groups, you can organize nodes in your dbt™️ DAG that share a logical connection (for example, by functional area) and assign an owner to the entire group.
* [**Model Access**](https://docs.paradime.io/app-help/best-practices/data-mesh-setup/model-access) - access configs allow you to control who can reference models.

## **Paradime dbt™️ Mesh features**

Paradime offers additional features to simplify the implementation of dbt™️ Mesh workflows, enabling data teams to work both independently and collaboratively.

### [**Paradime Graph Lineage**](https://docs.paradime.io/app-help/best-practices/broken-reference)

Providing a fully enabled cross-project lineage allows for a comprehensive exploration of lineage dependencies across various dbt™️ projects. 

This feature empowers users to gain deeper insights, track data transformation processes, and identify interconnections among multiple projects, enhancing overall data transparency and workflow efficiency.

### [**Paradime Data Catalog**](https://docs.paradime.io/app-help/best-practices/broken-reference)

Enabling comprehensive search and streamlined discovery of dbt™️ public models originating from the linked "producer" project. 

This feature allows users to efficiently locate and utilize shared dbt models, enhancing collaboration and the overall data workflow within the connected project environment.

### [**Paradime Bolt**](https://docs.paradime.io/app-help/best-practices/broken-reference) 

Allowing dbt™️ runs to be triggered based on the activities of a connected "producer" dbt™️ project streamlines the workflow and enhances integration.

This capability ensures that changes or updates in the producer project can automatically initiate corresponding runs in consumer projects, promoting continuity and reducing the need for manual intervention.

### [**Paradime Column Level Lineage Diff**](https://docs.paradime.io/app-help/documentation/bolt/ci-cd/lineage-diff) 

The Column Lineage Diff Analysis in Paradime lets users track changes in a Pull Request and see their impact on columns in the consumer project. This ensures users have visibility into dependencies and modifications.

By leveraging this functionality, users can identify and address potential breaking changes early, leading to smoother integration and deployment. This enhances data integrity and reliability by ensuring compatibility between producer and consumer projects during changes.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.paradime.io/app-help/best-practices/data-mesh-setup.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.