Event-driven o workflow-based: scegliere l'architettura giusta

Abstract (EN)

Process automation in SMEs comes in two architectural flavors: event-driven, where actions are triggered by state changes propagated through a message bus, and workflow-based, where a process engine explicitly models and executes sequences of steps. The two are not interchangeable. Event-driven systems scale better and decouple producers from consumers, but make process visibility harder. Workflow engines make the process explicit and auditable, but introduce a central coordinator that can become a bottleneck. This article describes when each architecture fits, using examples from production deployments in Italian and Spanish SMEs.