Difference between call and start Orchestration

BizTalk assigns one thread for every orchestration; even if you are using parallel shape inside your orchestration!

When you use Call Orchestration shape vs Start Orchestration shape?

The way BizTalk handles messages internally is different when it comes to calling or starting orchestrations.

Calling an Orchestration will use the same thread to run another orchestration while using Start Orchestration will create a new thread to run the started orchestration.

A Call Orchestration returns the control back to the caller. A Start Orchestration shape starts the orchestration in a non-deterministic way.

As a conclusion, Calling an Orchestration will be a synchronous operation where the caller waits for a response, while Start Orchestration is asynchronous operation.

Call Orchestration

  1. Will reduce latency as call orchestration doesn’t go via MessageBox
  2. Possible to pass all types of parameters
  3. Call shape will tightly bound orchestration

Start Orchestration

  1. Allows to execute orchestrations asynchronously
  2. Will increase latency as start orchestration call goes via MessageBox
  3. Possible to pass all types of parameters. No return param is supported
  4. Start shape will tightly bound orchestration

Short hint

If you call an orchestration from another project you have to set the Type Modifier Property to public. Otherwise, the orchestration will not show up in the dialog where to choose the orchestration you call.

Tags: BizTalk | Orchestration

Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

Leave a Reply

Your email address will not be published. Required fields are marked *

BizTalk360
BizTalk Server

Over 500+ customers across
30+ countries depend on BizTalk360

Learn More
Serverless360
Azure

Manage and monitor serverless
components effortlessly

Learn More
Atomicscope
Business Users

Monitor your Business Activity in iPaaS
or Hybrid integration solutions

Learn More

Back to Top