Overcome the Biggest Barriers to Digital Transformation

Discover 3 factors you can’t ignore that drive change in businesses

Drafting Your Camunda Cloud Architecture – Part 2: Service Integration Patterns With BPMN And Camunda Cloud

When automating processes you typically integrate systems and services, or in other words you orchestrate various APIs. In order to achieve this you not only have different technical possibilities (also described in part 1 of this blog post series: Connecting The Workflow Engine With Your World), but also can choose between various modeling possibilities in BPMN. This post will give you an overview and advice on how to decide between alternatives.

IMPORTANT: This blog post is based on capabilities of Camunda Cloud 1.0. New features might open up new possibilities and will influence the recommendations – please check regularly for updates.

This post is part of a series of blog posts around best practices for Camunda Cloud:

You might also be interested in general BPMN modeling best practices which are documented in the Camunda Platform Best Practices, namely:

Communication Patterns

Let’s briefly set the scene by looking at the three typical communication patterns to integrate systems.

  1. Request/response using synchronous communication styles: You use a synchronous protocol, like HTTP, and block for the result.
  2. Request/response using asynchronous communication styles: You use asynchronous communication, for example by sending messages via a message broker, but wait for a response message right after. Technically, these are two independent asynchronous messages, but the sender blocks until the response is received, hence logically making it a request/response.
  3. Asynchronous messages or events: If a peer service needs a long time to process a request, the response is much later than the request, say hours instead of milliseconds. In this case the response is typically handled as a separate message. Additionally, some of your services might also wait for messages or events that are not connected to a concrete request, especially in event-driven architectures.

The following table gives a summary of the three options.

Synchronous request/responseAsynchronous request/responseAsynchronous messages or events
Business levelSynchronousSynchronousAsynchronous
Technical communication styleSynchronousAsynchronousAsynchronous
ExampleHTTPAMQPAMQP, Apache Kafka

You can dive more into communication styles also in the webinar “Communication Between Loosely Coupled Microservices (slides, recording, and FAQ)”.

Integrating Services With BPMN Tasks

Let’s first look at using BPMN tasks to handle these communication patterns, before diving into BPMN events later in this post.

Service Task

The service task is the typical element to implement synchronous request/response calls, such as REST, gRPC or SOAP. You should always use service tasks for synchronous request/response.

Send Task

Note: In Zeebe 1.0 the send task is not yet supported and needs to be replaced by a service task for the moment. Support for the send task will follow soon (planned in version 1.1 in summer 2021).

Technically, send tasks behave exactly like service tasks. But the alternative symbol makes the meaning of sending a message easier to understand for some stakeholders.You should use send tasks for sending asynchronous messages, like AMQP messages or Kafka records.

There is some grey area whenever you call a synchronous service that then sends an asynchronous message. A good example is email. Assume your process does a synchronous request/response call to a service that then sends an email to inform the customer. The call itself is synchronous because it gives you a confirmation (acknowledgement, or ACK for short) that the email has been sent. Now is the “inform customer” task in your process a service or a send task?

This question is not easy to answer and depends on what your stakeholders understand more intuitively. The more technical people are, the more you might tend towards a service task, as this is technically correct. The more you move towards the business side, the more you might tend to use a send task, as business people will consider sending an email an asynchronous message. In general we tend to let the business win – as it is vital that business stakeholders understand business processes.

However, if you follow a microservice (or service-oriented architecture) mindset you might argue that you don’t need to know exactly how customers are informed within the process. Hiding the information if the notification is synchronous or asynchronous is good to keep your process model independent of such choices, making it more robust whenever the implementation of the notification service changes. This is a very valid concern too, often leading to long discussions about which symbol to choose.

My recommendation is simple: In case you can’t easily reach a conclusion, save time and simply use a service task.

You could also argue to use send tasks to invoke synchronous request/response calls when you are not interested in the response. However, this is typically confusing and I recommend not to use send tasks in this case.

Receive Task

A receive task waits for an asynchronous message. Receive tasks should be used for incoming asynchronous messages or events, like AMQP messages or Kafka records.

Receive tasks can be used to receive the response in asynchronous request/response scenarios, which is discussed next.

Service Task vs. Send/Receive Task Combo for Request/Response

For asynchronous request/response calls you can use a send task for the request, and a following receive task to wait for the response:

You can also use a service task, which is sometimes unknown even to advanced users. A service task can technically wait for a response that happens at any time, a process instance will wait in the service task, as it would in the receive task.

Deciding between these options is not completely straightforward, I’ve included a table below that lists the decision criteria to help you with that. But let me first discuss both options. And as a general rule-of-thumb I recommend the service task as the default option, for synchronous and asynchronous request/response calls. The beauty of service tasks is that you remove visual clutter from the diagram, which makes it easier to read for most stakeholders.

This is ideal if the business problem requires a logically synchronous service invocation. It allows you to ignore the technical details about the protocol on the process model level.

The typical counter-argument is that asynchronous technical protocols might lead to different failure scenarios that you have to care about. For example, when using a separate receive task, readers of the diagram almost immediately start to think about what happens if the response will not be received. But this also has the drawback, that now business people might start discussing technical concerns, which is not necessarily good. Furthermore, I find this to be a questionable argument, as synchronous REST service calls could also timeout. This is exactly the same situation, just “deeper” in network abstraction layers (every form of remote communication uses asynchronous messaging somewhere down in the network stack). So on a technical level you should always think about these failure scenarios, even when using service tasks, as I addressed in my talk about 3 common pitfalls in microservice integration and how to avoid them. On a business level, you should be aware of the business implications of technical failures, but not discuss or model all the nuts and bolts around it.

There are also technical implications of this design choice that need to be considered. Some of the technical considerations are subject to change over time as Camunda Cloud evolves – please double check when you read this at later points in time!

Technical Implications of Using Service Tasks

You can keep a service task open and just complete it later when the response arrives. But in order to complete the service task you need the job instance key from Zeebe. This is an internal ID from the workflow engine. You can either:

  • Pass it around to the third party service which sends it back as part of the response message, or
  • Build some kind of lookup table, where you map your own correlation information to the right job key.

Note: Later versions of Zeebe might provide query possibilities for this job key based on user controlled data, which might falsify this restriction.

Using workflow engine internal IDs can lead to problems. For example, you might cancel and restart a process instance because of operational failures, which can lead to a new ID. Outstanding responses cannot be correlated any more in such instances. Or you might run multiple workflow engines which can lead to internal IDs only being unique within one workflow engine. All of this might not happen, but the nature of an internal ID is that it is internal and you have no control over it – which bears some risk.

In practice, however, using the internal job instance key is not a big problem if you get responses in very short time frames like milliseconds. Whenever you have more long running interactions, you should consider using send and receive tasks, or build your own lookup table that can also address the above mentioned problems.

This is also balanced by the fact that service tasks are simply very handy. The concept is by far the easiest way to implement asynchronous request/response communication. The job instance key is generated for you and unique for every message interchange. You don’t have to think about race conditions or idempotency constraints yourself. Timeout handling and retry logic are built-in the service task implementation of Zeebe. And there is also a clear API to let the workflow engine know of technical or business errors.

Technical Implications of Using Send And Receive Tasks

Using send and receive tasks means to use the message concept built into Zeebe. This is a powerful concept to solve a lot of problems around cardinalities of subscriptions, correlation of the message to the right process instances, and verification of uniqueness of the message (idempotency).

When using messages you need to provide the correlation id yourself. This means that the correlation ID is fully under your control. But it also means that you need to generate it yourself and make sure it is unique. You will most likely end up with generated UUIDs.

You can leverage message buffering capabilities, which means that the process does not yet need to be ready-to-receive the message. You could for example do other things in between. At the same time you have to use message buffering to avoid the following race condition which I call the “overtaking response message problem”. I described an example in chapter nine of Practical Process Automation, a customer scenario where a SOAP call had a synchronous acknowledgement, but the real response was a JMS message:

The response message typically arrived before the SOAP request returned (for whatever technical reasons). In this case, the process instance was not ready-to-receive the response, which is not a problem if the message is buffered for at least a few milliseconds.

Using messages has more implications. It typically means that you will not get an exception right away if a message cannot be correlated, as it is simply buffered. This leaves you in charge of dealing with messages that can never be delivered. Retries are not built-in, leading to loops being modeled to retry service calls. And at least in the current Zeebe version 1.0, there is no possibility to trigger error events for a receive task, which means you need to model error messages as response payload or separate message types – both are discussed later in this post.

A final note for high-performance environments: These powerful messaging capabilities do not come for free and require some overhead within the engine. For pure request/response calls that return within milliseconds, none of the features are truly required. If you are looking to build a high-performance scenario, using service tasks instead of message correlation for request/response calls you can tune your overall performance or throughput. But as with everything performance related, the devil is in the detail, so please reach out to us to discuss such a scenario in more depth.

Summary And Recommendations

The following table summarizes the possibilities and recommendations.

CaseSynchronous request/response

Asynchronous request/response
Selected BPMN elementService TaskSend TaskService Task Send + Receive Task
Technical implications

Behaves like a service task
A unique correlation ID is generated for you 

You don’t have to think about race conditions or idempotency

Timeout handling and retry logic are built-in

API to flag business or technical errors
Correlation ID needs to be generated yourself, but is fully under control

Message buffering is possible but also necessary

Timeouts and retries need to be modeled

BPMN errors cannot be used

Very intuitive Might be more intuitive for fire and forget semantics, but can also lead to discussions
Removes visual noise which helps stakeholders to concentrate on core business logic, but requires use of internal job instance keys
Removes visual noise which helps stakeholders to concentrate on core business logic, but requires use of internal job instance keysMore visual clutter, but also more powerful options around correlation and modeling patterns
Default option, use unless it is confusing for business stakeholders (e.g. because of fire and forget semantics of a task)Use for fire and forget semantics, unless it leads to unnecessary discussions, in this case use service task instead
Use when response is within milliseconds and you can pass the Zeebe-internal job instance key around
Use when response is within milliseconds and you can pass the Zeebe-internal job instance key aroundUse when the response will take time (> some seconds),  or you need a correlation id you can control

Integrating Services With BPMN Events

Instead of using send or receive tasks, you can also use send or receive events in BPMN.

Let’s first explore when you want to do that and afterwards look into some more advanced patterns that become possible with events.

Tasks vs. Events

The execution semantics of send and receive events is identical with send and receive tasks, so you can express the very same thing with tasks or events.

However, there is one small difference that might be relevant: Only tasks can have boundary events, which allows to easily model when you want to cancel waiting for a message:

Despite this, the whole visual representation is of course different. In general, tasks are easier understood by most stakeholders, as they are used very often in BPMN models. However, in certain contexts, such as event-driven architectures, events might be better suited as the concept of events is well understood. Especially, if you apply domain-driven design (DDD) and discuss domain events all day long, it might be intuitive that events are clearly visible in your BPMN models. Another situation better suited for events is if you send events to your internal reporting system besides doing “the real” business logic. Our experience shows that the smaller event symbols are often unconsciously treated as less important by readers of the model, leading to models that are easier to understand.  

Note that in Zeebe 1.0 the send task is not yet supported and needs to be replaced by a service task for the moment. Support for the send task will follow soon (planned for version 1.1 in summer 2021).

Send taskReceive taskSend eventReceive event
Support in ZeebeNot yet available, planned for 1.1YesNot yet availableYes
RecommendationPrefer tasks over eventsUse only if you consistently use events over tasks and have a good reason for doing so (e.g. event-driven architecture)

Note that the choice about events vs. commands also needs to be reflected in the naming of the element, as a task emphasizes the action (e.g. “wait for response”) and the event reflects what happened (e.g. “response received”).

Handling Different Response Messages

Very often the response payload of the message will be examined to determine how to move on in the process.

In this case, you receive exactly one type of message for the response. As an alternative, you could also use different message types, to which the process can react differently. For example, you might wait for the validation message, but also accept a cancellation or rejection message instead:

This modeling has the advantage that it is much easier to see the expected normal flow of the process (which I call the happy path), with exceptions deviating from it. On the other hand, this pattern mixes receive tasks and events in one model, which can confuse readers. And you should also keep in mind that it only works for a limited number of non-happy messages.

To avoid the task/event mixture you could use a so-called event-based gateway instead, this gateway waits for one of a list of possible message types to be received:

We typically try to avoid the event-based gateway, as it is hard to understand for non-BPMN-professionals. At the same time it shares the downside of the first pattern with the decision gateway after the receive task: the happy path cannot be easily spotted.

As a fourth possibility you can add event sub processes, which get activated whenever some event is received while the process is still active in some other area. In the above example you could just model the happy path and model all deviations as event sub processes.

This pattern is pretty handy, but also needs some explanation to people new to BPMN. It has one downside you need to know: Once your process instance moves to the sub process, you can’t easily “go back” to the normal flow. To some extent this problem can be solved by advanced modeling patterns like shown in the “allow for order cancellation any time” example.

At the same time the event sub process has a super power that is worth mentioning: You can now wait for cancellation messages in whole chunks of your process – it could arrive anytime.

Receive task with boundary eventsPayload and XOR-gatewayEvent-based gatewayEvent sub process
Understandability by various stakeholdersEasyVery easyHardMedium
AssessmentLimitation on how many message types are possibleHappy path not easily visible______________________________________________Might need some explanation for readers of the model
RecommendationUse when it is important to see message types in the visual, limit to two boundary message eventsUse when there are more response types or if the response type can be treated as a resultTry to avoidUse if you need bigger scopes where you can react to events

Message Type On The Wire != BPMN Message Type

I want to add one important detail to the above discussion of message response patterns: The message type used in BPMN models does not have to be exactly the message type you get on the wire. When you correlate technical messages, e.g. from AMQP, you typically write a piece of glue code that receives the message and calls the workflow engine API. This was described in part 1 of this blog post series, including a code example. In this glue code you can do various transformations, for example:

  • Messages on different message queues could lead to the same BPMN message type, probably having some additional parameter in the payload indicating the origin.
  • Some message header or payload attributes could be used to select between different BPMN message types being used.

While I would not consider it best practice to be as inconsistent as possible between technical message types and BPMN message types, the flexibility of a custom mapping might be beneficial in some cases.

Hiding Technical Complexity Behind Call Activities

Whenever technical details of one service integration becomes complicated, you can think of creating a separate process model for the technicalities of the call and use a call activity in the main process.

An example is given in chapter seven of Practical Process Automation:

In the customer scenario, a document storage service was long running, but could not do a real callback or response message for technical reasons (in short: firewall limitations). As a result, the document storage service needed to be regularly polled for the response. In the customer scenario, this was done by a “document storage adapter” process, that leveraged workflow engine features to implement the polling every minute, and especially the persistent waiting in between. In the main business process, this technical adapter process was simply invoked via a call activity, meaning no technicalities bloated the diagram.


This blog post walked you through BPMN modeling possibilities around service integration. You can see that service tasks in general are a good choice, but also that there are situations where you might want to switch to send and receive tasks or events. So as always – it depends – but I hope you gained a better understanding of the factors it depends on.

You can find more information about workflow engines and integration challenges in my latest book Practical Process Automation with O’Reilly, and Real-Life BPMN might also be a good read to broaden your BPMN skills.

Subscribe to me on Twitter to ensure you see part three of this series, which will describe how to write “good” job workers for Camunda Cloud.