Deployments comparison
Understand the available capabilities and some of the compatibility, scalability, and security aspects of the IBM® Business Automation Workflow traditional and IBM Business Automation Workflow on containers deployments before you choose the deployment that aligns with your business needs.
| Capability | Traditional environment | Container environment |
|---|---|---|
| CI/CD GitHub and JFrog integration | Yes | Yes |
| Scalable and resilient | Traditional WebSphere® Application Server Scaling | Yes |
| API Key support for exposed REST services | No | Yes |
| Built-in PostgreSQL database (based on EDB PostgreSQL) Note: 25.0.1.0 EDB Postgres is not supported in 25.0.1.0. You must use an external
PostgreSQL for the Identity Management (IM) service, Platform UI (Zen service), and Business Teams
Service (BTS).
|
No (DB2® built-in) | Yes |
| Exposing service flows and processes as asynchronous operations of REST services | No | Yes |
| Exposing service flows and processes as Kafka services | No | Yes |
| Exposing service flows and processes as MQ services | No | Yes |
| Importing business objects in Workflow Process Designer | No | Yes |
| OAuth client credential flow support for external REST service invocation | No | Yes |
| Process federation on containers (federation between traditional and containers) | N/A | Yes |
| Support for OpenAPI 3.0 objects without properties | No | Yes |
| Transaction support in service flows | No | Yes |
| Workflow automation services | No | Yes |
| Business Automation Workflow Advanced capabilities (for example, BPEL, SCA, MFC) | Yes | No |
| Business Automation Insights (monitoring) | Yes | Yes |
| Intelligent Task Prioritization | Yes | Yes |