<?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 Arjan Geertsema on Medium]]></title>
        <description><![CDATA[Stories by Arjan Geertsema on Medium]]></description>
        <link>https://medium.com/@arjangeertsema?source=rss-882c9d4109b4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*eZ3e_YdtdBuby2NQIOismA.jpeg</url>
            <title>Stories by Arjan Geertsema on Medium</title>
            <link>https://medium.com/@arjangeertsema?source=rss-882c9d4109b4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:55:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arjangeertsema/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[BizDevOps, aligning business and IT]]></title>
            <link>https://arjangeertsema.medium.com/bizdevops-aligning-business-and-it-ea00ada05966?source=rss-882c9d4109b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea00ada05966</guid>
            <category><![CDATA[bpmn]]></category>
            <category><![CDATA[workflow-automation]]></category>
            <category><![CDATA[solution-architecture]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-architecture]]></category>
            <dc:creator><![CDATA[Arjan Geertsema]]></dc:creator>
            <pubDate>Fri, 08 Oct 2021 10:02:58 GMT</pubDate>
            <atom:updated>2021-10-26T12:19:16.237Z</atom:updated>
            <content:encoded><![CDATA[<p>I see a lot of companies struggling in delivering technical products which meet business expectations. With BizDevOps the goal is to restore the natural order: technical product development driven by business intent.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*bFFhbVbSWaVC5C1_hbkzsA.png" /></figure><p>I have almost twenty years experience in digital product development where I have learned a lot by making mistakes. Over the years I have discovered that some mistakes are more stubborn than others. These mistakes have one thing in common: we failed to deliver what the customer really needed.</p><p>Interpretation of an intent is very difficult. First you have to figure out what the real intent is (the question behind the question) and then several people will translate the outcomes into a product. All these layers of translation add to the risk of misinterpretation, which in turn may result in a product which does not meet customer expectation despite all good intentions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/949/1*k3uJfZY05k_uQqX0YNFyvQ.png" /><figcaption>copyright <a href="http://www.projectcartoon.com/">ww.projectcartoon.com</a> under the <a href="http://www.projectcartoon.com/about/">Creative Commons Attribution 3.0 Unported License</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/953/1*IbTT8FOYbvLm2TisvipzfA.png" /><figcaption>drawing game: draw what you feel, copyright <a href="https://www.youtube.com/watch?v=NI43U9UpkQo">youtube.com</a></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8kM7U575bL3p0Y5250zJIw.png" /><figcaption>whisper game: pass along the words</figcaption></figure><p><strong>WHAT vs HOW</strong></p><p>When working on technical products the responsibilities within the organization are typically divided between the business (WHAT) and engineering (HOW). To make things work they need to understand each other and accept that there is a natural hierarchy: the business is the customer and engineering the supplier. Therefore the business is in the lead.</p><p>This is often not the case in the real world. The business lacks the tools and knowledge to fully communicate their business intent without the need of interpretation by their engineers resulting in endless discussions. Most of these discussions are also HOW related regarding topics like Kafka, Azure, AWS, etc.. Unless you are working at one of these companies these topics are never business related and should not be discussed with business people present. And yes the same applies to our favorite HOW topic of all: micro services. All these topics are all HOW related implementation details.</p><p>I am sure this all sounds familiar, but how do we solve this? The solution is easy when you are working on digital products: enable the business to create the code so that the business intent is clear and does not need interpretation. Asking the business to write code sounds like a lot to ask. But in reality, when using the right tools and with some help from the right people, this is surprisingly easy.</p><p>With living documentation engineers only have to focus on the implementation, which is what they excel in. Living documentation is the missing piece in this WHAT vs HOW puzzle.</p><p><strong>Living documentation</strong></p><p>With living documentation the business is responsible for documenting its business intent. This documentation is scoped to a business domain. A business domain is a standalone (business) autonomous entity and speaks its own business language. With digital products the anatomy of a business domain is surprisingly uniform:</p><blockquote>A domain delivers one or more products which are consumed via an interface and realized with business processes. Business processes use data to operate and trigger applications to fulfill use cases.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lLWsrcQRUrmHzTqoj1Y5NA.png" /><figcaption>anatomy of a business domain</figcaption></figure><p>Because these interfaces are business interfaces rather than technical interfaces it is only logical that the business owns them. With <a href="https://www.synion.nl/blog/bizdevops/living-documentation.html">living documentation</a> the business is responsible for the documentation of these business interfaces. The engineers use the documented interfaces to generate code. The main <a href="https://www.synion.nl/blog/bizdevops/living-documentation.html">living documentation</a> citizens are:</p><ul><li>Business processes in <a href="https://www.bpmn.org/">BPMN format</a>;</li><li>Process related user interaction in <a href="https://json-schema.org/">json schema</a> format;</li><li>Process related commands and queries in <a href="https://www.openapis.org/">openapi format</a>;</li><li>Process related events in <a href="https://www.asyncapi.com/">asyncapi format</a>;</li><li>Additional process related business requirements in <a href="https://en.wikipedia.org/wiki/Behavior-driven_development">BDD format</a> (given, when, then);</li></ul><p>The business process is the most important linking pin between business and engineering:</p><ul><li>It is something that is understood by everyone;</li><li>It gives context to a use case;</li><li>It is free from details enabling high level business discussions;</li><li>You can zoom out to see even more context when the process is part of an end to end process;</li></ul><p>The <a href="https://www.synion.nl/blog/bizdevops/living-documentation.html">living documentation</a> is written in plain text and maintained in a .git repository. This also makes it possible to work with multiple people on multiple features at the same time. And all changes are tracked automatically. Widely available tooling for merge requests can be used for reviewing and commenting.</p><p>The plaint text documentation is automatically transformed into a user friendly website. This website is accessible for the entire organization and shows the current state of the business domain as well as the features being worked on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f7AvYtWfqVhiaMs5nmsmFg.png" /><figcaption>Example of a living process documentation. <a href="https://www.synion.nl/blog/bizdevops/living-documentation.html">Webpage can be found here.</a></figcaption></figure><p>Because the <a href="https://www.synion.nl/blog/bizdevops/living-documentation.html">living documentation</a> is used by engineering to generate code it is always up to date. The generated code explicitly communicates business intent and business language: fully aligning business and engineering.</p><p>To successfully implement BizDevOps and <a href="https://www.synion.nl/blog/bizdevops/living-documentation.html">living documentation</a> business and engineering must embrace these new WHAT vs HOW boundaries and accept thier new responsibilities.</p><p>A BizDevOps coach can help the organization with this transition. This person is someone who understands business as well as engineering and can operate on all levels in the organization. This person has a cross domain scope and therefore is able to challenge decisions and is able coach business as well as engineering.</p><p><strong>Closing notes</strong></p><p>With BizDevOps and <a href="https://www.synion.nl/blog/bizdevops/living-documentation.html">living documentation</a> anyone who wants to change the WHAT is forced to request the business for a change. In my experience these requests for change are the most interesting- and crucial moments in the BizDevOps lifecycle. This is when the right discussions, all related to WHAT, take place with the right people and often result in a surprising outcome.</p><p>With the strict separation between WHAT and HOW I am not suggesting to lockout engineering from the business cycle. This blog is all about ownership, responsibilities and context. Everyone needs to be aware of this when engaging in a discussion.</p><p>Please also read my next blog post “Hexagonal architecture, a business driven software architecture” which explains how engineering can implement and embrace <a href="https://www.synion.nl/blog/bizdevops/living-documentation.html">living documentation</a> features.</p><p><a href="https://www.linkedin.com/in/arjan-geertsema-051ab66/">Follow me on LinkedIn</a> to be notified about an upcoming webinar regarding BizDevOps.</p><p>I love getting your feedback. Comment below or <a href="/service/mailto:arjan@synion.nl">send me an email</a>.</p><p>Need help with implementing BizDevOps in your organization? <a href="/service/mailto: arjan@synion.nl">Reach out to me</a>, maybe I can help!</p><p>Thank you <a href="https://medium.com/u/41646ef41593">Bernd Rücker</a> and <a href="https://medium.com/u/8a40a2e6d36">Cyrille Martraire</a> for sharing your inspirational thoughts regarding BizDevOps and living documentation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea00ada05966" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zeebe and .Net, a love story…]]></title>
            <link>https://arjangeertsema.medium.com/zeebe-and-net-a-love-story-28475f988a79?source=rss-882c9d4109b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/28475f988a79</guid>
            <category><![CDATA[csharp]]></category>
            <category><![CDATA[camunda]]></category>
            <category><![CDATA[zeebe]]></category>
            <category><![CDATA[service-orchestration]]></category>
            <category><![CDATA[dotnet]]></category>
            <dc:creator><![CDATA[Arjan Geertsema]]></dc:creator>
            <pubDate>Sat, 04 Sep 2021 08:52:02 GMT</pubDate>
            <atom:updated>2021-09-06T12:00:55.270Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h3>Zeebe and .Net, a love story…</h3><p>Service orchestration is an important part of the micro service puzzle. With <a href="https://camunda.com/products/cloud/workflow-engine/">Zeebe</a> and the <a href="https://github.com/arjangeertsema/zeebe-client-csharp-bootstrap">zb-client-bootstrap extension for .Net</a> your life as a .Net micro service developer just got a lot easier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kmtngjvbm7gmxEqZfx1woQ.png" /></figure><p><strong>Choreography v.s. Orchestration</strong></p><p>When working with micro services you typically have two integration options: service choreography and service orchestration.</p><p>With service choreography services publish and subscribe to events. In theory the publisher is highly decoupled from its subscribers because they do not care if, when and who consumes the events, which is great. In practice things can be less ideal. Often event consumption is not optional, Furthermore there can be also an (hidden) order in which events need to be consumed often within a certain time frame.</p><p>With service orchestration an orchestrator sends commands to services: the orchestrator tells the service when and what to do. These commands can be visualized in a workflow. In BPM these commands are called tasks. Tasks can be synchronous or asynchronous.</p><p><strong>Workflows, Camunda, Zeebe?</strong></p><p><a href="https://github.com/camunda-cloud/zeebe">Zeebe</a> (by Camunda) is an opensource workflow engine which runs ISO standard <a href="https://camunda.com/products/camunda-platform/modeler/">BPMN </a>2.0 workflows. <a href="https://github.com/camunda-cloud/zeebe">Zeebe</a> scales horizontally, is language agnostic, fault tolerant and is highly available. It has built-in state management, retry policy support and audit logging which makes your life as a developer a lot easier, especially when you are working with micro services.</p><p><a href="https://github.com/camunda-cloud/zeebe">Zeebe</a> is a service orchestrator but it uses events internally. A job is published in queue whenever a task in a workflow instance is activated. Services can subscribe to jobs of a certain type. Multiple service instances can subscribe to the same type (competing consumers) and because the services are decoupled from <a href="https://github.com/camunda-cloud/zeebe">Zeebe</a>, services can be created in any language.</p><p><a href="https://camunda.com/products/cloud/workflow-engine/">Zeebe</a> is <a href="https://github.com/camunda-cloud/zeebe">opensource</a> and available as a <a href="https://camunda.com/products/cloud/">hosted service</a> or as a <a href="https://hub.docker.com/r/camunda/zeebe/">docker container</a> which you can host yourself.</p><p><strong>.Net job handling</strong></p><p>So for the developer it all boils down to handling jobs: input|output. With the <a href="https://github.com/arjangeertsema/zeebe-client-csharp-bootstrap">zb-client-bootstrap</a> this is easy. This package uses the <a href="https://www.nuget.org/packages/zb-client">zb-client</a> internally and ads logic so that job handlers are automatically discovered, hosted and wired to <a href="https://github.com/camunda-cloud/zeebe">Zeebe</a>.</p><p>Now, show me the money!</p><p><em>To start, add the nuget package to your project:</em></p><pre>dotnet add package zb-client-bootstrap</pre><p><em>Then bootstrap Zeebe :</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/e50472a047a7de813e3864aad62116f2/href">https://medium.com/media/e50472a047a7de813e3864aad62116f2/href</a></iframe><p>Let me explain what is happening here. BootstrapZeebe()will scan every assembly starting with ‘SimpleAsyncExample’ for job handlers. Every handler will automatically be added to the service collection, hosted in a IHostedServiceinstance and wired to <a href="https://github.com/camunda-cloud/zeebe">Zeebe</a>.</p><p>A job handler is a class which implements the IAsyncJobHandler&lt;TJob&gt;interface. This interface is generic and expects a job type which extends AbstractJob.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/25e5d378732412f76422e7b91052beeb/href">https://medium.com/media/25e5d378732412f76422e7b91052beeb/href</a></iframe><p><em>Create a workflow:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VfgHDRgEcV2xyRD7eg0aXA.png" /><figcaption>simple-process.bpmn</figcaption></figure><p><em>And lastly, add your job and job handler:</em></p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/b1d68e56f31c1d322f8f0f28fefe4b9b/href">https://medium.com/media/b1d68e56f31c1d322f8f0f28fefe4b9b/href</a></iframe><p>This is it. The task of type ‘DoSomething’ in any workflow instance is now handled by the DoSomethingHandler. The Zeebe job is automatically completed when the job is handled resulting in activating the next step in the workflow. Unhandled exceptions are also automatically sent to <a href="https://github.com/camunda-cloud/zeebe">Zeebe</a> resulting in the activation of the retry policy.</p><p><strong>Response values</strong></p><p>But there is more. Workflows can make decisions based on information. Information can be added as variables to the workflow instance. Typically this information is added when completing a job. Therefore it is also possible to complete a job with a response. This is done by adding a second type to the IAsyncJobHandler&lt;TJob, TResponse&gt;. The response is automatically serialized and passed to <a href="https://github.com/camunda-cloud/zeebe">Zeebe</a> when completing the job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CrshFHUHkXMgqRRG8xRSwQ.png" /><figcaption>simple-process-with-variable.bpmn</figcaption></figure><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/33448ac54e04106051ecd6eb8135e59e/href">https://medium.com/media/33448ac54e04106051ecd6eb8135e59e/href</a></iframe><p>Property of type boolean is automatically added to the workflow instance making it possible to add the following condition to the decision flow =Property=true</p><p><strong>Business exceptions</strong></p><p>Exceptions are not only technical; they also live in the business domain. Therefore it is possible to throw business exceptions inside the job handler resulting in an error automatically being send to <a href="https://github.com/camunda-cloud/zeebe">Zeebe</a>. A business exception is any exception which extends JobException. Business exceptions can be handled in the workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*evwnX-aHfz0Rv7MTH8-MpQ.png" /><figcaption>simple-process-with-exception.bpmn</figcaption></figure><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bd7ea58c66a89a33e92c0a2f92fec098/href">https://medium.com/media/bd7ea58c66a89a33e92c0a2f92fec098/href</a></iframe><p><strong>Closing notes</strong></p><p>I want to thank the people at <a href="https://camunda.com/">Camunda</a> for their excellent products. I am a big BizDevOps fan. Workflows are an important part of the BizDevOps puzzle and <a href="https://camunda.com/">Camunda</a> nailed it.</p><ul><li>Want to know more about workflow automation? Download <a href="https://medium.com/u/41646ef41593">Bernd Rücker</a> excellent e-book “<a href="https://page.camunda.com/wp-practical-process-automation-book-digital-release">Practical Process Automation</a>”;</li><li>Checkout my opensource .Net extension at <a href="https://github.com/arjangeertsema/zeebe-client-csharp-bootstrap">GitHub</a>;</li><li>There is also <a href="https://github.com/arjangeertsema/zeebe-client-csharp-bootstrap/blob/main/src/Zeebe.Client.Bootstrap/Abstractions/IJobHandler.cs">a synchronous job handler</a> available;</li><li>You can configure job handling by adding <a href="https://github.com/arjangeertsema/zeebe-client-csharp-bootstrap/tree/main/src/Zeebe.Client.Bootstrap/Attributes">attributes</a> to the job;</li><li>The service lifetime is configurable by adding the <a href="https://github.com/arjangeertsema/zeebe-client-csharp-bootstrap/blob/main/src/Zeebe.Client.Bootstrap/Attributes/ServiceLifetimeAttribute.cs">ServiceLifeTimeAttribute</a> to the job handler;</li></ul><p>Go play around with <a href="https://github.com/camunda-cloud/zeebe">Zeebe</a>, <a href="https://camunda.com/products/camunda-platform/modeler/">BPM</a> and, if you are into .Net, the <a href="https://www.nuget.org/packages/zb-client-bootstrap/">zb-client-bootstrap nuget package</a>.</p><p>Have fun!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=28475f988a79" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>