<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Docs on Microworkflows</title><link>http://www.microworkflows.org/docs/</link><description>Recent content in Docs on Microworkflows</description><generator>Hugo</generator><language>en-us</language><atom:link href="http://www.microworkflows.org/docs/index.xml" rel="self" type="application/rss+xml"/><item><title>Implications</title><link>http://www.microworkflows.org/docs/implications/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>http://www.microworkflows.org/docs/implications/</guid><description>&lt;h1 id="implications"&gt;Implications&lt;a class="anchor" href="#implications"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Not using a workflow engine also means that the features they typically provide won&amp;rsquo;t be available. Let&amp;rsquo;s look at some of them, and what doing without them means for your system.&lt;/p&gt;
&lt;h2 id="separate-observation-from-control"&gt;Separate Observation From Control&lt;a class="anchor" href="#separate-observation-from-control"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A commonly stated advantage of workflow engines is the &amp;ldquo;end-to-end&amp;rdquo; view over the process.&lt;/p&gt;
&lt;p&gt;There isn&amp;rsquo;t really a reason though for mixing controlling the process (that is, knowing the whole process, the current state an invocation of the process is in, and driving the process by initiating the next step) with observation. We generally try to keep things simple in software architecture, and want to avoid coupling unrelated concerns.&lt;/p&gt;</description></item><item><title>Examples</title><link>http://www.microworkflows.org/docs/examples/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>http://www.microworkflows.org/docs/examples/</guid><description>&lt;h1 id="examples"&gt;Examples&lt;a class="anchor" href="#examples"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="order-process"&gt;Order Process&lt;a class="anchor" href="#order-process"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;h2 id="submit-your-own-examples"&gt;Submit Your Own Examples!&lt;a class="anchor" href="#submit-your-own-examples"&gt;#&lt;/a&gt;&lt;/h2&gt;</description></item><item><title>Microworkflows And ..</title><link>http://www.microworkflows.org/docs/related/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>http://www.microworkflows.org/docs/related/</guid><description>&lt;h1 id="microworkflows-and-"&gt;Microworkflows And ..&lt;a class="anchor" href="#microworkflows-and-"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;You may find the thought of basing your system on events and microworkflows, and not relying on any coordinator or workflow engine, a bit mind-bending. In fact, I believe the challenge lies not in technology or tools, but in the mindset. I&amp;rsquo;d like to provide some thought experiments that may make it easier to understand the philosophy behing microworkflows.&lt;/p&gt;
&lt;h2 id="-unix-philosophy"&gt;.. Unix Philosophy&lt;a class="anchor" href="#-unix-philosophy"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Think about the command line tools in your shell. They follow the &lt;a href="https://en.wikipedia.org/wiki/Unix_philosophy"&gt;Unix Philosophy&lt;/a&gt;, which has been summarized as:&lt;/p&gt;</description></item><item><title>Orchestration vs. Choreography</title><link>http://www.microworkflows.org/docs/orchestration-vs-choreography/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>http://www.microworkflows.org/docs/orchestration-vs-choreography/</guid><description>&lt;h1 id="orchestration-vs-choreography"&gt;Orchestration vs. Choreography&lt;a class="anchor" href="#orchestration-vs-choreography"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;If you&amp;rsquo;ve searched the internet for suggestions how to implement complex workflows with microservices, you most certainly have come across pages and talks that discuss &amp;ldquo;orchestration&amp;rdquo; versus &amp;ldquo;choreography&amp;rdquo;. Yet - outside of this page - you won&amp;rsquo;t find these terms on microworkflows.org. Why?&lt;/p&gt;
&lt;h2 id="what-does-orchestration-vs-choreography-mean"&gt;What does &amp;ldquo;orchestration vs. choreography&amp;rdquo; mean?&lt;a class="anchor" href="#what-does-orchestration-vs-choreography-mean"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;h2 id="the-problem-with-orchestration-vs-choreography"&gt;The problem with &amp;ldquo;orchestration vs. choreography&amp;rdquo;&lt;a class="anchor" href="#the-problem-with-orchestration-vs-choreography"&gt;#&lt;/a&gt;&lt;/h2&gt;</description></item><item><title>Further Reading</title><link>http://www.microworkflows.org/docs/references/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>http://www.microworkflows.org/docs/references/</guid><description>&lt;h1 id="further-reading"&gt;Further Reading&lt;a class="anchor" href="#further-reading"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;h2 id="articles"&gt;Articles&lt;a class="anchor" href="#articles"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="https://blog-codecentric-de.translate.goog/wer-microservices-richtig-macht-braucht-keine-workflow-engine-und-kein-bpmn?_x_tr_sl=de&amp;amp;_x_tr_tl=en&amp;amp;_x_tr_hl=en&amp;amp;_x_tr_pto=wapp"&gt;If you do microservices correctly, you don&amp;rsquo;t need a workflow engine or BPMN&lt;/a&gt; &amp;ndash; Great blog post from 2015. It&amp;rsquo;s a Google Translate link, the original is in German: &lt;a href="https://blog.codecentric.de/wer-microservices-richtig-macht-braucht-keine-workflow-engine-und-kein-bpmn"&gt;Wer Microservices richtig macht, braucht keine Workflow Engine und kein BPMN&lt;/a&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="https://itnext.io/refactor-from-monolith-workflow-to-micro-workflows-92afcc49c8ec"&gt;Refactor from Monolith Workflow to Micro-Workflows&lt;/a&gt; &amp;ndash; As far as I can tell, the author of this blog post coined the term &amp;ldquo;microworkflow&amp;rdquo;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;a href="https://www.ben-morris.com/orchestration-vs-choreography-for-microservice-workflows/"&gt;Orchestration vs choreography for microservice workflows&lt;/a&gt; &amp;ndash; find a quote from this blog post below.&lt;/p&gt;</description></item></channel></rss>