EAIGuide
  • Welcome to the Integration Handbook
  • The Basics
    • What Is Application Integration?
    • Types of Application Integration
      • Event-Driven Architecture (EDA)
      • B2B Integration (Business-to-Business Integration)
      • iPaaS (Integration Platform as a Service)
      • Middleware Integration
      • Data Integration
      • API-Led Integration
      • Hub-and-Spoke Integration (ESB)
      • Point to Point Integration
    • Enterprise Integration Patterns
      • Message Creation
        • Message
        • Request-Reply
        • Events
      • Message Routing
        • Pipes & Filters
        • Router
        • Splitter
        • Aggregator
        • Routing Slip
        • Scatter-Gatherer
      • Message Transformation
        • Content Enrich
        • Content Filter
        • Translator
        • Claim Check
        • Normalizer
        • Canonical Data Model
      • Message Channel
        • Send and Receive
        • Point to Point
        • Publish Subscribe
        • Invalid Message
        • Guaranteed Delivery
        • Dead Letter
        • Messaging Bridge
      • Message End Point
        • Send and Receive
        • Transactional
        • Polling
        • Event Driven
        • Dispatcher
        • Consumers
        • Durable Subscriber
        • Idempotent Receiver
      • Messaging System Management
    • Integration Center Of Excellence
      • Innovation and Agility
      • Consistency and Quality
      • Cost Savings
      • Efficiency and Speed
      • Risk Management
  • Design and Development
    • Project Human Resources
      • Integration Architect
      • Integration Developer
      • Project Manager
      • Functional SME
      • Functional Tester
      • Technical Tester
      • Training & Support
    • Process Flow Design
      • Business Process Mapping
      • Functional Design
      • Technical Design
    • Process Flow Development
      • Coding Standards
      • Naming Conventions
      • Data Preparation for Testing
      • Unit Testing
      • Integration Testing
      • Go-Live Preparation
  • Monitoring & Support
    • Maintaining Integrations
      • Monitoring Messages
      • Message Logging
      • Error Handling
      • Retrigger Messages
      • Alerting Frameworks
      • Documentation
      • Version Control
    • Continuous Improvement
      • Performance Engineering
Powered by GitBook
On this page
  • Benefits of the Point-to-Point Integration Method
  • Disadvantages of the Point-to-Point Integration Method
  • Example: Salesforce and Mailchimp Point-to-Point Integration
  • Scenario
  • Integration Process
  • Challenges

Was this helpful?

  1. The Basics
  2. Types of Application Integration

Point to Point Integration

Advantages and dis-advantages of direct integration.

PreviousHub-and-Spoke Integration (ESB)NextEnterprise Integration Patterns

Last updated 4 months ago

Was this helpful?

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.

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.

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:

For the above three app connections, n=3. So f(3) = 3 x (3 - 1) = 6 possible point-to-point connections.

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.

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.

f(n)=n×(n−1)f(n)=n×(n−1)f(n)=n×(n−1)
Logic in direct integration methodology
Logic in direct integration methodology
Three applications direct Integration possibility
Three applications direct Integration possibility
Sync Contacts between SalesForce and MailChimp
Sync Contacts between SalesForce and MailChimp
Challenge in Point to Point Contacts Sync
Challenge in Point to Point Contacts Sync