Visão Geral

Curso Camunda for Architects, é direcionado a arquitetos de software e outras equipes técnicas que precisam ganhar experiência prática no uso de Camunda e ferramentas associadas para construir soluções robustas de mecanismo de decisão e fluxo de trabalho. 

Você aprenderá como modelar processos de negócios usando Camunda Modeler e BPMN junto com a orquestração de elementos de processos de negócios, como microsserviços, funções sem servidor, decisões e até mesmo humanos.

Objetivo

Após realizar este Curso Camunda for Architects, você será capaz de:

• A justificativa para usar a Camunda
• Usando BPMN no Camunda Modeler
• Camunda Orquestração Básica
• Autonomia, limites e isolamento
• Equilibrando Orquestração e Coreografia
• Mecanismos de fluxo de trabalho e desafios de integração
• Visibilidade do Processo
• A jornada para introduzir a automação de processos

Publico Alvo

Este curso é direcionado principalmente a:

• Diretores de TI,
• CTOs,
• Arquitetos de Software,
• Gerentes de Projetos de TI,
• Desenvolvedores de Software,
• Analistas de Negócios.

Pre-Requisitos

• Este curso não envolve codificação prática, mas um entendimento de software / web / aplicativos corporativos e / ou sistemas de negócios é altamente recomendado.

Materiais

Conteúdo Programatico

Introduction       

1. Process Automation
2. Workflow Engines and Executable Process Models
3. An example Business Scenario
4. Business Processes, Integration Processes, and Workflows
5. Business and IT Collaboration
6. Business Drivers and the Value of Process Automation
7. The Story of Camunda 

The Rationale for using Camunda

1. The Workflow Engine
2. Camunda Architecture
3. Additional Features of Workflow Platforms 
4. Operations Tooling
5. Task list Applications
6. Business Monitoring and Reporting
7. Intro to the Course case study

Using BPMN in Camunda Modeler

1. Modelling at different layers: level 0, Level 1, Level 2…
2. Start and End Events, tokens and Control Flow
3. Sequence Flows: Controlling the Flow of Execution
4. Tasks and Gateways
5. Events: Waiting for Something to Happen
6. Message Events: Waiting for a Trigger from the Outside
7. Exercise: Modelling the case study in BPMN

Camunda Orchestration Basics

1. Orchestration Software
2. Service-Oriented Architecture (SOA) Services
3. Microservices
4. Serverless Functions (FAAS)
5. Orchestrate Decisions
6. Decision Model and Notation (DMN)
7. Orchestrate Humans
8. Task Assignment

Camunda Architecture        

1. Architecture Trade-Offs
2. Decentralized Engines 
3. Ownership of Process Models
4. Using the Workflow Engine as a Communication Channel
5. Developer Experience and Continuous Delivery
6. Evaluating Workflow Engines
7. Demo: A quick look at the underlying XML representation of the process

Autonomy, Boundaries, and Isolation   

1. Strong Cohesion and Low Coupling 
2. Domain-Driven Design, Bounded Contexts, and Services
3. Boundaries and Business Processes 
4. Long-Running Behaviour
5. Helps You Defend Boundaries 
6. How Processes Communicate Across Boundaries
7. Call Activities: Handy Shortcuts Only Within the Boundary
8. Hands-on: Using a Call activity

Balancing Orchestration and Choreography                                 

1. Event-Driven Systems
2. Contrasting Orchestration and Choreography
3. Messages, Events, and Commands
4. The Direction of Dependency
5. Hands-on: Implementing a simple choreography

Workflow Engines and Integration Challenges       

1. Communication Patterns for Service Invocation
2. Aggregating Messages
3. Synchronous Facades Hiding Asynchronous Communication 
4. Transactions and Consistency 
5. Eventual Consistency
6. The Saga Pattern and Compensation 
7. Chaining Resources by Using the Outbox Pattern
8. Eventual Consistency Applies to Every Form of Remote Communication

Process Visibility    

1. Getting the Data
2. Observability and Distributed Tracing Tools
3. Data Warehouses, Data Lakes, and Business Intelligence Tools 
4. Process Mining 
5. Allowing for a Deeper Understanding
6. Hands-on: Making sense of distributed tracing data

The Journey to Introduce Process Automation  

1. Anti-patterns
2. Bottom-up Versus Top-down Adoption
3. From Project to Program: Scaling Adoption 
4. Establishing a Center of Excellence 
5. Roles and Skill Development