| description | title | ms.custom | ms.date | ms.service | ms.reviewer | ms.suite | ms.topic |
|---|---|---|---|---|---|---|---|
Learn more about: Scaled-Out Processing Hosts |
Scaled-Out Processing Hosts |
06/08/2017 |
biztalk-server |
article |
A scaled-out processing host improves performance and provides high availability by isolating orchestration functionality onto two or more separate host computers. This isolation lets you add multiple computers to a processing host for redundancy. A processing host in Microsoft [!INCLUDEbtsBizTalkServerNoVersion] runs one or more host instances that coordinate various business processes and creates an instance of programmatic objects for orchestrations.
The following figure shows a [!INCLUDEbtsBizTalkServerNoVersion] deployment that provides high availability for the processing host by having two computers that are running instances of the processing host. Note that in this figure the receiving and sending hosts are not highly available.
In this configuration, the work for processing orchestrations is load balanced between two [!INCLUDEbtsBizTalkServerNoVersion] computers that have instances of the processing host and run independently of each other. If one computer encounters errors or fails, [!INCLUDEbtsBizTalkServerNoVersion] automatically uses the host instance on the other computer to process remaining orchestrations.
BizTalk Server maintains orchestration state centrally in Microsoft [!INCLUDEbtsSQLServerNoVersion], and not locally on each [!INCLUDEbtsBizTalkServerNoVersion] computer. By persisting the state in the MessageBox database, [!INCLUDEbtsBizTalkServerNoVersion] overcomes the limitation of relying on a single processing host instance to process the orchestration, and lets any processing host instance process the orchestration. If an error occurs while [!INCLUDEbtsBizTalkServerNoVersion] processes an orchestration, another instance of the same processing host can complete the orchestration from the last persisted state.