Publishing “Practical Process Automation” With O’Reilly
Tags: cloudnative, processautomation, architecture, book
Published: 2021-04-07 19:32:49

---
title: Publishing “Practical Process Automation” With O’Reilly
published: true
date: 2021-03-25 12:03:07 UTC
tags: cloudnative, processautomation, softwarearchitecture,book
canonical_url: https://blog.bernd-ruecker.com/publishing-practical-process-automation-with-oreilly-db993db68411
---

#### A Book about Orchestration and Integration in Microservices and Cloud-Native Architectures

It is done and I am happy to share that my new book called [“Practical Process Automation” is officially published by O’Reilly](https://learning.oreilly.com/library/view/practical-process-automation/9781492061441/).

In this book, I distilled [my practical experience implementing process automation solutions from the last two decades](https://berndruecker.io/bio.php).

![](https://cdn-images-1.medium.com/max/325/1*1CX5KNsoi3YhBWE_3UFjAA.png)

### What You Will Find In The Book

- A general **introduction to process automation** and the different forms of automation
- An explanation of how **developer-friendly process automation** can be applied in modern system architectures and software development practices
- A hands-on guide to **lightweight workflow engines and BPMN** as the core elements to make this happen
- **Architecture guidelines** and best practices to implement your own process solutions
- A discussion of typical misconceptions around process automation and orchestration
- Information on how to **balance orchestration and choreography** in modern architectures
- Advice on how process automation can help you with **challenges around distributed systems**
- Information on how to design your **adoption journey** , from the very first grassroots initiative, over lighthouse projects to company-wide adoption with a center of excellence.

### Who This Book is For?

This book targets **software developers, software engineers** , and software or system **architects** that want to learn about process automation.

### Why You Should Read This Book

1. Digital transformation is happening everywhere and automation a must.
2. Many processes are tailor-made to an organization’s needs, as this allows them to differentiate from the competition. Therefore they cannot be addressed by off-the-shelf application software.
3. Automating these processes is complex and requires software engineering, but with specific characteristics and requirements.
4. You will need a developer-friendly way to automate processes, leveraging lightweight workflow engine technology. This is exactly what this book explains to you.

### Some Praise

I am happy to get super positive feedback so far, some of which I can even share with you here:

> Weaving together ideas from microservices, event-driven systems, and Domain-Driven Design, this book describes when, why, and how to effectively leverage workflows within a modern software architecture. Taking a pragmatic practitioner’s approach, it uses real-world examples and explores the pros and cons of multiple alternative patterns in detail. It should be on every architect’s bookshelf.

**Randy Shoup, VP Engineering and Chief Architect at eBay**

> Bernd has championed and delivered developer-friendly process automation tools for the best part of the last decade. Now, in this pragmatic new book, Bernd brings that wealth of experience to show how process automation models, methods, and tools can be applied to tame the complexity of microservices and cloud-native architectures which are becoming ever more prevalent in today’s technology landscape. I highly recommend this book for architects and developers who want to add process automation thinking to their design toolkit.

**Richard Tarling, Digitization & Workflow Engineering Co-lead at Goldman Sachs**

> Process automation has often been viewed as the antithesis of modern, agile software development: snazzy “doodleware” demos that don’t scale to real use cases, poor testability, and version control only for the fortunate ones. No one better than Bernd to show us that this perception has little to do with workflow and process automation but merely with past implementations. Seeing process automation as an extension of well-established software development methods and architectures breathes a much welcome breeeze of fresh air into the field.

**Gregor Hohpe, author of Enterprise Integration Patterns and The Software Architect Elevator**

### How to Get It?

At this moment the book is available electronically only, the print version should be available within 2 or 3 weeks.

- [**Get This Book From O’Reilly**](https://learning.oreilly.com/library/view/practical-process-automation/9781492061441/) as part of your O’Reilly subscription. You can also start[a free 30 days trial](https://learning.oreilly.com/get-learning/?code=PPAER20).
- [**Get Your Free Electronic Copy**](https://page.camunda.com/wp-practical-process-automation-book-early-release?utm_medium=referral&utm_source=processautomationbook), as [Camunda](https://camunda.com/) was so kind to sponsor that a free electronic copy is available.

The book should be available [**on Amazon**](https://www.amazon.com/Practical-Process-Automation-Orchestration-Microservices/dp/149206145X) and other book stores soon.

You can find the books website here: [https://ProcessAutomationBook.com](https://ProcessAutomationBook.com)

![](https://cdn-images-1.medium.com/max/1024/1*8JCdpATDls7iShcbUJ5zeA.png)

### And Finally Some Useless Facts

A lot of blood, sweat, and tears went into this book. It was a project that took around two years to complete, from shaping the thoughts to the discussions with O’Reilly before actually writing anything. I thought you might be interested in some really useless facts around the book.

First of all let me describe the **tech stack** I used for writing, based on the [O’Reilly Atlas stack](https://docs.atlas.oreilly.com/) with Git, Asciidoc, and some magic to produce the final artifacts. I used Visual Studio Code to write. Furthermore, I used[Drawboard PDF on my Microsoft Surface to re-read and edit](https://twitter.com/berndruecker/status/1242037143402360832). That setting worked like a charm for me.

<style>body[data-twttr-rendered="true"] {background-color: transparent;}.twitter-tweet {margin: auto !important;}</style>

>  — [@berndruecker](https://twitter.com/berndruecker/status/1242037143402360832)

<script src="//platform.twitter.com/widgets.js" charset="utf-8"></script><script>function notifyResize(height) {height = height ? height : document.documentElement.offsetHeight; var resized = false; if (window.donkey && donkey.resize) {donkey.resize(height);resized = true;}if (parent && parent._resizeIframe) {var obj = {iframe: window.frameElement, height: height}; parent._resizeIframe(obj); resized = true;}if (window.location && window.location.hash === "#amp=1" && window.parent && window.parent.postMessage) {window.parent.postMessage({sentinel: "amp", type: "embed-size", height: height}, "*");}if (window.webkit && window.webkit.messageHandlers && window.webkit.messageHandlers.resize) {window.webkit.messageHandlers.resize.postMessage(height); resized = true;}return resized;}twttr.events.bind('rendered', function (event) {notifyResize();}); twttr.events.bind('resize', function (event) {notifyResize();});</script><script>if (parent && parent._resizeIframe) {var maxWidth = parseInt(window.frameElement.getAttribute("width")); if ( 500 < maxWidth) {window.frameElement.setAttribute("width", "500");}}</script>

Some dates:

- 2019-January-24: Date when I first drafted my initial idea of the book
- 2019-November-18: Date I signed the contract with O’Reilly
- 2019-November-19: Date of my first commit on the book sources
- 2021-March-15: Date of my last commit on the book sources
- 2021-March-1: 7Date when the final book hit the O’Reilly platform

In Git history, you can see how the content evolved over time.

![](https://cdn-images-1.medium.com/max/640/0*ZsSw3QaHfaqpftPt)

The bigger tech reviews happened around August 2020, so most things afterward were refactorings and re-arrangements. As you can see in the following table, this did not mean less work — probably the contrary.

![](https://cdn-images-1.medium.com/max/399/0*_M1ZVXxLHEmsk1Yn)

But the statistics also reveal that I was really good not to commit on the weekends!

![](https://cdn-images-1.medium.com/max/591/0*brzUVVw3LzIvfUJR)

By the way, in this graph, you can even see at what time we typically have our family dinner :-)

Some final numbers (please bear with me, some numbers might be not 100% accurate as I did relative straight forward techniques to get them):

- Number of commits: 409
- Number of words: 82,323
- Number of pages I planned to write: 180
- Number of pages I wrote: 264
- Number of times the term “process” is mentioned: 1827
- Number of times the term “workflow engine” is mentioned: 453
- Number of times the term “architecture” is mentioned: 185
- Number of times the term “microservice” is mentioned: 165
- Number of times the term “low code” is mentioned: 26
- Number of times the term “testing” is mentioned: 26

That’s all I have for now — I hope you will enjoy reading the book — and don’t hesitate to send feedback!

[Bernd Ruecker](http://berndruecker.io/) is co-founder and chief technologist of C[amunda](http://camunda.com/) as well as author or [Practical Process Automation with O’Reilly](https://processautomationbook.com/). He likes speaking about himself in the third-person. He is passionate about developer-friendly process automation technology. Connect via [LinkedIn](https://www.linkedin.com/in/bernd-ruecker-21661122/) or follow him on[Twitter](http://twitter.com/berndruecker/)_._ As always, he loves getting your feedback. Comment below or[send him an email](http://bernd.ruecker@camunda.com).

* * *