Camunda Training Course for Developers

Who should attend

The course is largely aimed at Software Developers but will also be beneficial for technical project managers, business analysts and software testers. We're also happy to tailor a bespoke course for your organisation in order to make sure the content and delivery is relevant and appropriate for your project requirements.

Prerequisites

An understanding of software / web / enterprise applications and / or business systems and some exposure to coding with a technology such as .NET, Java, JavaScript, Python, C++ would be strongly recommended.

Live, instructor-led online and on-site training

We appreciate that you need flexibility to fit in with new working situations - whether you're an individual, part of a distributed team, or simply have projects and deadlines to meet. 

Our remote training can take place online in a virtual classroom, with content split into modules to accommodate your scheduling challenges and meet your learning goals. Get in touch today to find out how we can help design a cost-effective, flexible training solution.

Introduction

• Process Automation
• The integration puzzles
• Workflow Engines and Executable Process Models
• An example Business Scenario
• Handling Long-Running Process behaviour
• Business Processes, Integration Processes, and Workflows
• Business and IT Collaboration
• Business Drivers and the Value of Process Automation
• A Brief History of Process Automation
• The Story of Camunda

The Rationale for using a Workflow Engine

• The Workflow Engine
• Core Capabilities
• Additional Features of Workflow Platforms
• A Process Solution
• An Executable Example
• Applications, Processes, and Workflow Engines
• Typical Workflow Tools in a Project’s Life Cycle
• Graphical Process Modeler
• Collaboration Tools
• Operations Tooling
• Task list Applications
• Business Monitoring and Reporting
• Intro to the Course case study

Modelling Language: BPMN

• Business Process Model and Notation (BPMN)
• Modelling at different layers: level 0, Level 1, Level 2…
• Start and End Events, tokens and Control Flow
• Sequence Flows: Controlling the Flow of Execution
• Tasks: Units of Work
• Gateways: Steering Flow
• Events: Waiting for Something to Happen
• Message Events: Waiting for a Trigger from the Outside
• Combining Process Models and Programming Code
• Publish/Subscribe to a Process
• Referencing Code in Process Models
• Using Prebuilt Connectors
• Model or Code?
• Testing Processes
• Versioning of Process Solutions
• Running Versions in Parallel
• Exercise: Modelling the case study in BPMN

Process Orchestration Basics

• Orchestration Software
• Service-Oriented Architecture (SOA) Services
• Microservices
• Nanoservices?
• Serverless Functions (FAAS)
• Modular Monoliths (aka the Modulith)
• Deconstructing the Monolith
• Orchestrate Decisions
• Decision Model and Notation (DMN)
• Decisions in a Process Model
• Orchestrate Humans
• Task Assignment
• The User Interface of User Tasks
• Orchestrate RPA Bots
• Orchestrate Physical Devices and Things

Using BPMN and the Workflow Engine

• Hardcoded Processes
• Batch Processing
• Data Pipelines and Streaming
• The Actor Model
• Stateful Functions
• Process Modelling Languages
• Workflow Patterns
• Benefits of Graphical Process Visualizations
• Textual Process Modelling Approaches
• Typical Concerns About Graphical Modelling
• Graphical Versus Textual Approaches
• Hands-on with the workflow engine

Solution Architecture

• When to Use a Workflow Engine
• Architecture Trade-Offs
• Running the Workflow Engine
• Decentralized Engines
• Sharing Engines
• Ownership of Process Models
• Using the Workflow Engine as a Communication Channel
• In-House Workflow Platforms
• Performance and Scalability
• Developer Experience and Continuous Delivery
• Evaluating Workflow Engines
• Demo: A quick look at the underlying XML representation of the process

Autonomy, Boundaries, and Isolation

• Strong Cohesion and Low Coupling
• Domain-Driven Design, Bounded Contexts, and Services
• Boundaries and Business Processes
• Respect Boundaries and Avoid Process Monoliths
• Foster Your Understanding of Responsibilities
• Long-Running Behaviour
• Helps You Defend Boundaries
• How Processes Communicate Across Boundaries
• Call Activities: Handy Shortcuts Only Within the Boundary
• Crossing Boundaries Is an API Call
• Decentralized Workflow Tooling
• Hands-on: Using a Call activity

Balancing Orchestration and Choreography

• Event-Driven Systems
• Emergent Behaviour
• Event Chains
• The Risk of Distributed Monoliths
• Contrasting Orchestration and Choreography
• Introducing Commands
• Messages, Events, and Commands
• Terminology and Definitions
• Avoiding Event Chains by Using Commands
• The Direction of Dependency
• Finding the Right Balance
• Deciding Whether to Use Commands or Events
• Mixing Commands and Events
• Designing Responsibilities
• Evaluating Change Scenarios to Validate Decisions
• Debunking Common Myths
• Commands Do Not Require Synchronous Communication
• Orchestration Does Not Need to Be Central
• Choreography Does Not Automatically Lead to More Decoupling
• The Role of Workflow Engines
• Hands-on: Implementing a simple choreography

Workflow Engines and Integration Challenges

• Communication Patterns for Service Invocation
• Synchronous Request/Response
• Asynchronous Request/Response
• BPMN and Being Ready to Receive
• Aggregating Messages
• Poisoned and Dead Messages
• Synchronous Facades Hiding Asynchronous Communication
• Transactions and Consistency
• Eventual Consistency
• Business Strategies to Handle Inconsistency
• The Saga Pattern and Compensation
• Chaining Resources by Using the Outbox Pattern
• Eventual Consistency Applies to Every Form of Remote Communication
• The Importance of Idempotency
• Exercise: Building and executing a Saga

Business–IT Collaboration

• A Typical Project
• SCRUM, Kanban, DevOps basics
• Including All the People: BizDevOps
• Development
• Synergy between Business and Operations
• The Power of One Joined Model
• From a Process Pyramid to a House
• Who Does the Modelling?
• Creating Better Process Models
• Extracting (Integration) Logic into Subprocesses
• Distinguishing Between Results, Exceptions, and Errors
• Increasing Readability

Process Visibility

• The Value of Process Visibility
• Getting the Data
• Leverage Audit Data from Your Workflow Engine
• Model Events to Measure Key Performance Indicators
• Status Inquiries
• Understanding Processes That Span Multiple Systems
• Observability and Distributed Tracing Tools
• Custom Centralized Monitoring
• Data Warehouses, Data Lakes, and Business Intelligence Tools
• Process Mining
• Process Event Monitoring
• Current Market Dynamics
• Setting Up Process Reporting and Monitoring
• Typical Metrics and Reports
• Allowing for a Deeper Understanding
• Hands-on: Making sense of distributed tracing data

The Journey to Introduce Process Automation

• Understanding the Adoption Journey
• Anti-patterns
• A Success Story and Epic Failures
• The Pattern of Successful Adoption Journeys
• Different Journeys for Different Scenarios
• Starting Your Journey
• Bottom-up Versus Top-down Adoption
• Proofs of Concepts
• Presenting the Business Case
• Don’t Build Your Own Platform
• Dos and Don’ts Around Reuse
• From Project to Program: Scaling Adoption
• Perception Management: What Is Process Automation?
• Establishing a Center of Excellence
• Managing Architecture Decisions
• Decentralized Workflow Tooling
• Roles and Skill Development