sf-agent-framework/sf-core/tasks/integration-pattern-selection.md

AI Agent Orchestration Framework for Salesforce Development - Two-phase architecture with 70% context reduction

# Integration Pattern Selection

## Purpose

Select appropriate integration patterns for Salesforce implementations based on
requirements, constraints, and best practices.

## Instructions

1. **Requirements Analysis**
   - Document integration scenarios
   - Identify data volume and frequency
   - Define latency requirements
   - Assess reliability needs
   - Determine security constraints

2. **Pattern Evaluation**
   - Review available patterns:
     - Request-Reply (Synchronous)
     - Fire-and-Forget (Asynchronous)
     - Batch Data Sync
     - Remote Call-In
     - UI Update
     - Data Virtualization
   - Match patterns to requirements
   - Consider hybrid approaches

3. **Technology Selection**
   - Evaluate integration technologies:
     - REST/SOAP APIs
     - Platform Events
     - Change Data Capture
     - Outbound Messages
     - Salesforce Connect
     - MuleSoft
   - Assess middleware needs
   - Consider API management

4. **Architecture Design**
   - Design integration architecture
   - Plan error handling approach
   - Define retry mechanisms
   - Design monitoring strategy
   - Plan data transformation

5. **Performance Optimization**
   - Consider API limits
   - Plan bulk operations
   - Design caching strategies
   - Optimize payload sizes
   - Implement pagination

6. **Security Design**
   - Define authentication methods
   - Plan authorization approach
   - Design encryption strategy
   - Implement audit logging
   - Consider compliance needs

## Input Requirements

- Integration requirements
- System landscape
- Data flow diagrams
- Performance requirements
- Security policies
- Compliance needs

## Output Format

- Integration Pattern Design:
  - Pattern selection matrix
  - Architecture diagrams
  - Technology recommendations
  - Implementation approach
  - Security design
  - Monitoring plan

## Common Patterns

- **Request-Reply**: Real-time queries
- **Fire-and-Forget**: Event notifications
- **Batch Sync**: Large data transfers
- **Remote Call-In**: External updates
- **Pub-Sub**: Event streaming
- **ESB**: Enterprise service bus

## Selection Criteria

- Timing requirements
- Data volume
- Reliability needs
- Error handling
- Transaction support
- Performance impact
- Maintenance complexity

## Best Practices

- Choose simplest viable pattern
- Consider total cost of ownership
- Plan for failure scenarios
- Design for monitoring
- Document pattern rationale
- Test at production scale
- Review regularly