> For the complete documentation index, see [llms.txt](https://docs.primeur.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.primeur.com/our-philosophy/the-challenge/data-integration-vs-application-integration.md).

# Data Integration vs Application Integration

If you are thinking of data exchange as a model where one application sends data **directly** to another application, you are already in point-to-point mode and thinking about **Application Integration**. Here, the exchange is direct: application A sends data to application B. In this type of integration, **data producers and data consumers are closely interconnected**.

<figure><img src="/files/wp3hEbgnhUFvVA9D5PUN" alt="" width="563"><figcaption></figcaption></figure>

**Data Integration** is different and smarter than Application Integration because it uses an **intermediary** that picks up and delivers data at the appropriate time to the various applications. Forget the unmanageable intertwining of data exchanges between applications. They do not even talk to each other, they talk to a single interlocutor. With Data Integration, **applications are decoupled** and everything is clearly more manageable.

<figure><img src="/files/Gr929BPVhCF03Smb06yk" alt="" width="563"><figcaption></figcaption></figure>

To summarize, these are the **main differences between these two methodologies**:

| Application Integration                                                                                                                                 | Data Integration                                                                                                                             |
| ------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| Point-to-point connections (coupled applications)                                                                                                       | Intermediary connections (decoupled applications)                                                                                            |
| <p>Essential approach when:<br>- You need to use application capabilities<br>- You need to exchange data in real-time with transactional commitment</p> | <p>Approach adoptable when:<br>- You need only data, not application functionality<br>- A near real-time or batch exchange is sufficient</p> |
| You need to change the interfaces of the applications involved                                                                                          | No intervention is made in any way on the applications, which remain independent                                                             |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.primeur.com/our-philosophy/the-challenge/data-integration-vs-application-integration.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.