Learn IT with Shikha Blogs

  Enterprise Content Management is not only about storing documents. In real enterprise environments, documents usually participate in business processes such as: document review and approval; contract approval; invoice processing; employee onboarding; purchase requests; policy review; compliance validation; records management; document publishing; exception handling. This is where Alfresco Workflow Automation with Activiti BPMN becomes important. Alfresco combines enterprise content management capabilities with workflow and process management, allowing organizations to automate content-centric business processes. Instead of manually emailing documents between users, organizations can model the process using BPMN (Business Process Model and Notation) and allow the workflow engine to control task assignment, approvals, decisions, notifications and process completion. A simplified enterprise workflow can look like: Document Created → Review → Business Decision → Approval → Publish ...

  La gestion de contenu d’entreprise ne consiste pas uniquement à stocker des documents. Dans les environnements professionnels, les documents participent généralement à des processus métier tels que : la révision et l’approbation de documents; l’approbation de contrats ; le traitement des factures ; l’intégration des nouveaux employés ; les demandes d’achat ; la validation des politiques internes ; les contrôles de conformité ; la gestion des documents ; la publication de contenu ; la gestion des exceptions. C’est ici que l’automatisation des workflows Alfresco avec Activiti BPMN devient particulièrement utile. Alfresco associe la gestion de contenu d’entreprise à des capacités de workflow permettant d’automatiser les processus métier centrés sur les documents. Au lieu d’envoyer manuellement des documents par e-mail entre différents utilisateurs, les organisations peuvent modéliser leurs processus avec BPMN (Business Process Model and Notation) et laisser le moteur de workflow g...

🔹 This article provides a hands-on BPM training guide using Camunda 8. 👉 For conceptual learning and BPM basics, read: https://shikhanirankari.blogspot.com/2026/04/guide-de-formation-bpm-avec-camunda-8.html ## Introduction Learning BPM with Camunda 8 requires practical experience in modeling, deploying, and running workflows. Instead of only understanding concepts, developers must work with real BPMN diagrams, decision tables, and execution environments. In this guide, we focus on hands-on training with Camunda 8. ## 🔹 Scope of this Article This article covers: - BPMN modeling practice - workflow deployment - task execution - monitoring workflows - hands-on exercises 👉 This article focuses on practical training, not theoretical explanation. 👉 This article focuses on hands-on BPM training and practical implementation using Camunda 8. ## 🔹 Step 1: BPMN Modeling - Create process using Camunda Modeler - Use events, tasks, and gateways ## 🔹 Step 2: Deploy Workflow - Deploy BPMN to Ca...

Zeebe Architecture Overview ✍️ Introduction If you’re coming from Camunda 7 (DB-based engine) , understanding how Camunda 8 (Zeebe) stores workflow state is a game changer . Instead of storing process state in a relational database, Zeebe uses a distributed event-driven architecture — making it: ⚡ Highly scalable 🔁 Fault tolerant 🚀 Extremely fast 👉 Let’s break this down in a simple, practical way . 🧩 1. Core Idea: Event-Sourced State In Zeebe: ❌ No central database ✅ Workflow state = event stream (log of events) Every action in a workflow becomes an event : Process started Task activated Variable updated Task completed These events are written sequentially to a log . 📌 This is similar to Kafka-style architecture. 👉 Zeebe stores state as event streams on disk across brokers 🖼️ Event Stream Concept ⚙️ 2. How State is Actually Stored Let’s simplify: 🧱 Step-by-step Client sends command → via Gateway (REST/gRPC) Gateway routes to a Broker Broker writes an event: PROCESS_INSTANCE_C...

  Camunda vs Temporal vs Zeebe – Workflow Engine Comparison Choosing the right workflow engine is critical for building scalable, reliable, and maintainable business processes . Three popular options today are: Camunda Temporal Zeebe 👉 But which one should you use? In this guide, we compare them based on: Architecture Use cases Scalability Developer experience 🔹 1. Overview of Each Engine 🟢 Camunda BPMN-based workflow engine Strong modeling capabilities Best for business + IT collaboration 🔵 Temporal Code-first workflow engine Uses SDKs (Java, Go, etc.) Designed for developers 🟣 Zeebe Cloud-native workflow engine (by Camunda) Built for scalability Used in Camunda 8 🔹 2. Architecture Comparison Feature Camunda 7 Temporal Zeebe (Camunda 8) Type BPMN Engine Code-based Distributed Workflow Engine Storage Relational DB Event history Distributed log Execution Sync + Async Fully async Fully async Scaling Limited High Very high 🔹 3. Modeling Approach Camunda ✔ Visual BPMN modeling ✔...