<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Baptiste Lombard on Medium]]></title>
        <description><![CDATA[Stories by Baptiste Lombard on Medium]]></description>
        <link>https://medium.com/@baptiste.lmbrd?source=rss-9a78cc88d547------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3GjhogjTifQRYJXrGAVK_w.jpeg</url>
            <title>Stories by Baptiste Lombard on Medium</title>
            <link>https://medium.com/@baptiste.lmbrd?source=rss-9a78cc88d547------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 11:39:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@baptiste.lmbrd/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Exploring the Power of BPMN Workflow Engine: Insights from Our Camunda Journey]]></title>
            <link>https://medium.com/@baptiste.lmbrd/exploring-the-power-of-bpmn-workflow-engine-insights-from-our-camunda-journey-5bee617df1a7?source=rss-9a78cc88d547------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bee617df1a7</guid>
            <category><![CDATA[business-development]]></category>
            <category><![CDATA[orchestration]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[bpmn]]></category>
            <dc:creator><![CDATA[Baptiste Lombard]]></dc:creator>
            <pubDate>Fri, 23 Jun 2023 14:00:09 GMT</pubDate>
            <atom:updated>2023-06-23T14:00:09.172Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I_tms585pgxYuRrA" /><figcaption>Photo by <a href="https://unsplash.com/@dinoreichmuth?utm_source=medium&amp;utm_medium=referral">Dino Reichmuth</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>In this article, we explore the world of BPMN workflow engines, focusing on Camunda software. Discover the origins, benefits, and complexities we encountered during implementation and usage. Join us on our Camunda journey to uncover the transformative capabilities of this powerful BPMN workflow engine and how it permits us to succeed our digital transformation on the order orchestration.</p><h3><strong>It’s all a business story</strong></h3><p>BPMN (Business Process Model and Notation), is a standardized graphical notation for modeling business processes. It provides a visual representation of processes and workflows, enabling businesses to communicate and analyze their operations effectively.</p><p>This notation comes from BPMI (Business Process Management Initiative) who decided to create a standardized notation for process modeling in 2001 and was released in 2004. BPMI merged with the Object Management Group (OMG) in 2005 and became an ISO norm in July 2013.</p><p>The goal of BPMN is to provide a user-friendly way to represent and communicate complex business processes and their orchestration. It permits to make it understandable for all the society users, from the stakeholders to the developers who need to implement the business features.</p><p>In 2011, the BPMN notation went out of its cocoon to not be just a documentary file but something more. The introduction of more advanced features such as event sub-processes, message flows, and data objects enables the specification of executable processes. This means that BPMN models could be directly executed or automated using software tools, going beyond their original purpose as a visual representation.</p><h3><strong>And on our case?</strong></h3><p>For our project we chose to use Camunda software to implement a part of our business. Camunda provides a range of features, including workflow and process management (BPMN), decision automation (DMN), task management, user interfaces, monitoring and analytics, and integration capabilities.</p><p>It permits us to implement all the features of our order orchestration from the moment where the order is created on the merchant website to the delivery of the order or its cancellation.</p><p><strong>Orchestration vs Choreography</strong></p><p>When you begin to work with workflow, you quickly come aboard the notions of orchestration and choreography. The two notions come from the Saga pattern which is a way to handle data consistency with distributed architecture. And basically, you need to understand what you will do and why.</p><p><strong>Orchestration</strong></p><p>The principle of orchestration is to lead a distributed system. As an orchestrated system, you need to know which action is needed to do, who should do it and when. It manages and coordinates the different actions between the dependencies. The orchestration uses command driven communication, where the sender wants an action to be done, but the recipient doesn’t necessarily know who wants to do it.</p><p>You can use orchestration when you need to guarantee a list of execution done in a specific order, when you want to display a unified view of your microservice system or if you want to manage the life cycle of a service.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/1*duj9XFuvdJOLZnvRuCCoIQ.png" /><figcaption>Schema of an orchestration workflow</figcaption></figure><p><strong>Choreography</strong></p><p>At the opposite of the orchestration, the choreography takes place where every service knows what he has to do and when. The different components or microservices will interact with each other with well determined rules or triggers. The choreography uses event-driven communication, where events are states of objects that occurred in the past as a fact (ex: Payment succeed).</p><p>You can use choreography when you want to avoid bottlenecks or a single point of failure on your service, if you have independent microservices that can be autonomous or if you want to be able to plug &amp; play some services easily.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/732/1*Lu34OgujcK0hH9SiLV22DA.png" /><figcaption>Schema of a choreography workflow</figcaption></figure><p>You can read more about this here: <a href="https://camunda.com/blog/2023/02/orchestration-vs-choreography/">https://camunda.com/blog/2023/02/orchestration-vs-choreography/</a></p><p><strong>Then you chose orchestration or choreography?</strong></p><p>In our case, we used a bit of the two worlds to work on our workflow. In fact our workflow is generally here to orchestrate orders from their creation to the moment they are delivered, but some elements are kept as responsibility of other services.</p><p>One first part of our workflow was to validate the payment of the order to start notifying other services. Another service is in charge to validate the payments done and notify each new state of the payment through a Kafka topic.</p><p>When the payment is validated, the workflow is in charge to notify every service about the new existing order (ex: Customer notification, Invoice, Workshop Appointment, Supply).</p><p>At each change of the state of the order, an event is also sent in a specific topic. It is consumed by some services where the data of the order in different states is required to work with (ex: BI, Finances, Stocks). Here we are on a choreography approach.</p><p>In a second time, the workflow reacts to events until the end of the order. It reacts at the evolution state of the order, depending on the actions made from the supply or workshop service, and orchestrates various actions depending on the status he receives.</p><h3><strong>Why do we use it?</strong></h3><p><strong>Time-saving Solution</strong></p><p>Camunda proved to be a valuable choice for our project, particularly when faced with tight timelines. By using its workflow engine, we were able to reduce development and implementation time, avoiding the need to build a complete workflow engine from scratch.</p><p><strong>Unified Communication</strong></p><p>Camunda allows our entire team, from the Product Owner to the developers and Quality Assurance, to speak the same language when discussing processes. This ensures better understanding and collaboration among team members, as everyone shares a common understanding of the workflows.</p><p><strong>User-Friendly Interface</strong></p><p>The user interface permits us to simplify error handling and enhances our ability to understand what is happening during process execution. This feature enables us to quickly identify and address errors, as well as provide valuable feedback to our clients based on real-time information.</p><p><strong>Keep it generic!</strong></p><p>As we handle operations in multiple countries with unique needs, it permits us to keep most of the tasks generic and choose the moment of their execution. It allows us to maintain a generic approach while still accommodating specificity.</p><p><strong>Decision Tables (DMN)</strong></p><p>The inclusion of decision tables within Camunda’s capabilities has significantly improved our implementation process, especially in handling multiple variable decisions. For instance, we can easily select appropriate mail templates based on various factors, gaining better visibility and control over decision-making processes.</p><h3><strong>Easy to learn / hard to master?</strong></h3><p>During our journey with workflow and Camunda, we discovered some specificities that we didn’t expect. It was kind of easy to play with BPMN and begin a workflow responding to our first use cases, but it’s also a whole tool responding to particular rules and technical constraints. Here is some hints to take care of before beginning :</p><p><strong>Versioning</strong></p><p>Camunda works with versioning of the workflow. That means when you modify your workflow or a sub-workflow, you don’t change the workflow for the executions actually running. One option is to migrate the executions and transfer it on your newest action. But for that you will have to keep the exact same kind of tasks for the old workflow to the new one where the execution is waiting. You can also wait to terminate all your ongoing executions on your previous workflow but you will have to take care about the breaking change on the tasks or subprocess needed on your workflow. All your processes will always use the last version of the subprocess they call.</p><p><strong>Data Handling and Data Objects</strong></p><p>We began to work by thinking it was a good idea to give as variable our whole order data to the workflow execution. At first step, it was easy to add new conditions using this data and it permitted us to evolve quickly. With the first evolutions of our order data, we quickly saw the problem of capacity to evolve with this huge object used on all the workflows and tasks. So we changed to a dedicated data model fitting all the data needed for the workflow executed.</p><p><strong>Time-to-Live (TTLs) and Database</strong></p><p>After some time running on production, we began to be alerted about the big huge size of the database of Camunda. Two major things impacted that:</p><ul><li>The history time-to-live wasn’t set up on our workflow, so all the history data was stacking since the beginning. You can easily set up one manually on the workflow or use a variable to set it up globally.</li><li>All the xml or variable data of your workflows is also stocked in the database, take care to don’t use heavy data structure and cleanup your old version of workflows when they are not useful anymore.</li></ul><p>You can also set up a configuration to cleanup your history data on a specific time range. Don’t hesitate to do it from the beginning of the project.</p><p><strong>Mastery of BPMN</strong></p><p>It felt easy at first to use BPMN and to design basic behaviors, but as coding, you have always multiple ways to design the same behavior. Keep in mind that the workflow is not only an executable, but also a document that should be understood by everyone. it should be clear and easy to read. Take care to understand all the activities, conditions and events you can use for modeling your workflow. As coding, try to keep at maximum a clean “indentation” and respect this 2 rules:</p><ul><li>A condition should always be a question (ex: Is the invoice generated?).</li><li>A task action should always begin with a verb and respect the command that has to be done (ex: Generate invoice document).</li></ul><p>To sum up, BPMN workflow engines are nice tools that can centralize business logic in the core of your execution. It’s a time-saver on your development and permits to focus the communication on what’s really matter, your business.</p><p>Take time to understand how BPMN works and its rules, how the tool you will use works and understand how you can communicate with all the microservices you will work with. At the end, it will result a beautiful product how is really fun to work on. Tell us how it went for you!</p><p><strong>Reviewed by: </strong><a href="https://medium.com/@odupuis_61967">Olivia Dupuis</a>, <a href="https://medium.com/@nassim.bouazabia">Nassim Bouazabia</a>, <a href="https://medium.com/@jamalb">Jamal Bounasseh</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bee617df1a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>