External Tasks for Service Orchestration

July 26, 2016 at 05:00 PM (CET)

How you can leverage the external tasks pattern

The Camunda BPMN process engine supports two ways of executing service tasks:

  1. Internal Service tasks: Synchronous invocation of a service (locally or remotely)
  2. External Service tasks: Providing a unit of work in a list that can be polled by (external) workers

External (service) tasks work in a way that the process engine publishes a unit of work to a worker to fetch and complete. This pattern provide some very interesting advantages:

Temporal Decoupling: No need for Message Queues.

Polyglot Architectures: Easier to call Camunda REST API from a .NET client than expose a REST API on top of your .NET service so that Camunda might call it.

Better Scaling Patterns: Easier to start/stop workers that call Camunda REST API than set up a load balancing for your workers (services).

Connect Cloud BPM to On Premise Services: Easier to call Camunda REST API from behind a firewall than let Camunda BPM call your service behind the firewall.

Avoid Timeouts: Easier to handle long-running services since you do not need to implement an asynchronous service call / wait for callback.

In this webinar, we will look at some practical examples that will help you to apply the external task pattern in your own process applications, if appropriate.

Presented by Bernd Rücker

Bernd Rücker has been active in the BPM space for more than 10 years now. During this time he coached countless BPM projects, especially in terms of process automation using open source technologies. He is co-author of the bestselling book Real-Life BPMN and co-founder of camunda services GmbH.
Register now

Join the Camunda BPM Network to view a recording of this webinar for free!

Already a member? Log In here

By registering you accept our terms and conditions and agree to receive emails from Camunda. You can unsubscribe from these at any time.