Horizontal Scaling and Backend Capacity
Locate client, API and backend bottlenecks before promising scale-out gains; budget replica connection pools, externalize worker-dependent state and validate representative performance tests.
Describe when horizontal scaling of an API implementation is or is not likely to benefit response time and throughput as seen by API clients.
~7 min read · 8 practice questions
What the exam expects
- Distinguish isolated response time from throughput and queueing under load.
- Locate the limiting resource in the consumer, API implementation or dependency.
- Budget outbound connections across independently configured replicas.
- Make workflows independent of a particular CloudHub worker.
- Match autoscaling conditions to measured signals and validate capacity tests.
Horizontal scaling adds implementation instances; throughput measures completed work per time; response time includes waiting and execution; a connection pool maintains reusable connections with a configured limit. An API replica and its dependency have separate resource budgets (Backend response time, CloudHub availability, Pooling profiles). CloudHub examples below concern classic CloudHub workers, not an assumed CloudHub 2.0 replica contract.
Key facts
- Detail
- More API replicas do not divide one unchanged backend calculation.
- Detail
- More workers can reduce API-side queueing without splitting a single flow.
- Detail
- Additional callers can increase pressure without raising dependency throughput.
- Detail
- Provider replicas do not resize the client's outbound connection configuration.
- Detail
- Aggregate configured potential depends on replica count and per-pool caps.
- Detail
- External files and workflow references avoid dependence on one worker.
- Detail
- A higher maximum is a range change, not satisfaction of a CPU condition.
- Detail
- Changing the test tool requires executing all tests again.
Sources for this section (8)
- Backend response timedocs.mulesoft.com (opens in a new tab)
- CloudHub availabilitydocs.mulesoft.com (opens in a new tab)
- AWS retry guidanceaws.amazon.com (opens in a new tab)
- HTTP 1.9 referencegithub.com (opens in a new tab)
- Database referencedocs.mulesoft.com (opens in a new tab)
- CloudHub developmentdocs.mulesoft.com (opens in a new tab)
- CloudHub autoscalingdocs.mulesoft.com (opens in a new tab)
- Performance validationdocs.mulesoft.com (opens in a new tab)
- Why verify functional behavior before performance testing?
- When the load-test tool changes, which tests must run again?
- Why review ramp-up, tear-down and error-percentage settings before test execution?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the MuleSoft Platform Architect pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 47 lessons of the MuleSoft Platform Architect guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (8 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