Apache DolphinScheduler vs Workflow Engine

Apache DolphinScheduler is a free, open-source workflow orchestration platform for designing and running data workflows through visual directed-acyclic-graph interfaces or code. Workflows can be built with drag-and-drop tools or defined in Python, YAML, or the Open API. The project lists more than 30 task types, including Shell, SQL, Spark, Flink, Hive, Kubernetes, and HTTP. Scheduling supports cross-project and cross-workflow dependencies, pause and resume operations, and serial or parallel batch backfills. A decentralized multi-master, multi-worker design is described as increasing scheduling capacity with cluster size. Deployment options are standalone, cluster, and Kubernetes. Standalone is for evaluation, recommended for fewer than 20 workflows, and its in-memory H2 database is cleared when the service stops or restarts. Authentication includes password, LDAP, Casdoor SSO, and OAuth2, with administrator-managed resource controls. The security model assumes a trusted network.

Workflow Engine is an embeddable.NET library for managing business processes while saving their state in your database. It supports timers, audit history, and process versioning, and includes an HTML5 visual designer that can be embedded in an application. Designer packages are available for React, Angular, and vanilla JavaScript, with a documented Blazor integration. The core package supports.NET Framework 4.6.2 through.NET 10 and is deployed on-premises or in a customer's cloud. Supported databases include SQL Server, Azure SQL, PostgreSQL, MongoDB, Azure Cosmos DB, MySQL, Oracle, and SQLite. It imports BPMN 2.0 diagrams as native schemes, but does not export diagrams back to BPMN. Workflow Engine Free is licensed for personal, non-commercial use and costs nothing; it is limited to 10 schemas and 4 execution threads. Paid options include one-time licenses and subscriptions. NEO adds an HTTP API and multitenancy, while Workflow Server is a standalone Docker service called over HTTP. The core engine has no user store; authentication is the host application's responsibility.