# Point to Point Integration
A point-to-point Integration connects two or more applications directly. If there are two applications, namely A and B, and they need to exchange messages with each other, either application A or application B or both need to store the logic of message exchange, connection, etc. The developer needs to code this logic in the native language of Application A or the native language of Application B. Where this message exchange and connection logic resides depends upon the Pull or Push mechanisms.
Logic in direct integration methodology
Direct connections are simple to create and easy to use. This methodology offers both advantages and disadvantages. If the number of applications in an enterprise is less, these methods can be employed without much overhead. Generally, Enterprises have several applications that need the same type of messages synced to multiple applications. The use of different applications has only grown with the advent of the Software as a Service model. Almost all of them need message exchanges; direct connections can become unmanageable.
Three applications direct Integration possibility
The following formula can calculate the number of Ordered pairs of applications. If n = no. of applications that need to be connected in an enterprise, then:
$$
f(n)=n×(n−1)
$$
{% hint style="info" %}
For the above three app connections, n=3. So f(3) = 3 x (3 - 1) = 6 possible point-to-point connections.
{% endhint %}
## Benefits of the Point-to-Point Integration Method
* Low Cost of Development
* No additional Integration Skillset / Training for the team is necessary
* No need for extra software/license costs for Middleware
## Disadvantages of the Point-to-Point Integration Method
* Complexity of Integrations
* Tight Coupling between the applications
* If one application changes, another application should change
* More testing time
* Less code re-use as each application has to re-create the essential functions of Integration
## **Example: Salesforce and Mailchimp Point-to-Point Integration**
### **Scenario**
A company wants to automatically sync customer data from Salesforce (a CRM system) to Mailchimp (an email marketing platform) so that when new leads or contacts get added to Salesforce, they will automatically get added to a specific mailing list in Mailchimp.
### **Integration Process**
A direct connection between SalesForce and MailChimp is set. SalesForce's logic for sending data to MailChimp via API resides in SalesForce. A SalesForce trigger initiates the sync whenever a new contact is created or updated.
Sync Contacts between SalesForce and MailChimp
### **Challenges**
If the company wants to sync the contact information from SalesForce to other applications in the future, additional logic will need to be coded for every application that needs to be synced. This leads to a complex web of Integrations. Maintenance of such a web of connectivity can increase Integrations' operating expenses.
Challenge in Point to Point Contacts Sync
---
# 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://www.eaiguide.org/the-basics/types-of-application-integration/point-to-point-integration.md?ask=
```
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.