Recognize common integration problems, use cases, and technical solutions17% of the exam
Point-to-point, ESB and SOA integration tradeoffs
The tradeoffs MuleSoft describes as integration moved from point-to-point links and ETL tools through hub-and-spoke brokers to the ESB, and how SOA differs from microservices and API-led connectivity.
Classify and describe the tradeoffs of legacy and modern integration approaches.
~6 min read · 5 practice questions ·
What the exam expects
- Explain why point-to-point connections multiply as systems are added, and when a direct link is still adequate.
- Describe the hub-and-spoke broker model of EAI, its advantages and its weaknesses.
- Place the ESB in the history of EAI as the bus-based successor to brokers.
- Contrast ETL tools used for operational integration with an ESB's real-time, API-based connectivity.
- Distinguish SOA from microservices on culture and reuse, and say what MuleSoft recommends instead of choosing one.
Key terms:
- Point-to-point integration: a unique connector for each pair of systems that must communicate.
- EAI (enterprise application integration): a category of approaches that uses middleware to centralize and standardize integration.
- Broker (hub-and-spoke): a central engine through which all messages flow for transformation and routing.
- ESB (enterprise service bus): the mature bus-based EAI model that distributes integration tasks into separate components.
- SOA (service-oriented architecture): an architecture built around reusable services rather than entire applications.
Key facts
Point-to-point connector scope
- Detail
- One unique connector per pair of systems
Point-to-point at 3 and 5 components
- Detail
- 3 connections for 3 components, 10 for 5
Point-to-point at 10+ components
- Detail
- 45 or more connections
When point-to-point is adequate
- Detail
- 3 systems or fewer and no expected growth
Broker weakness
- Detail
- Single point of failure and bottleneck under heavy load
Broker project failures
- Detail
- As many as 70 percent (2003 study)
ETL orientation
- Detail
- Batch movement of large data volumes
SOA principles
- Detail
- Still valid today
- About how many point-to-point connections does MuleSoft say 8 or 9 systems need?
- Why does a security patch hurt a point-to-point network so badly?
- When did ETL tools become the go-to choice for operational integration?
- Why did top-down SOA programs slow release cycles?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Integration Foundations pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 37 lessons of the MuleSoft Integration Foundations guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (5 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both