Activiti is a light-weight workflow and Business Process Management (BPM) Platform targeted at business people, developers and system admins. Its core is a super-fast and rock-solid BPMN 2 process engine for Java. It's open-source and distributed under the Apache license. Activiti runs in any Java application, on a server, on a cluster or in the cloud. It integrates perfectly with Spring, it is extremely lightweight and based on simple concepts.
Hi,
I've spent 2 weeks to try activiti cloud v7.1.0.M6 and v7.6.0 with docker and run it successfully. I think the way to cloud is great. Embedded workflow will be eliminated in the future.
However, I have some suggestions about activiti cloud.
In the architect way, I think deep integration with keycloak is a bad choice.
Most of developers here just want a workflow solution which is easier to integrate with their existing user authentication system instead of a solution to rebuild their authentication system.
Secondly, you can say that keycloak can work as an identity providers with any existing user authentication systems. But it will take more time for them to learn keycloak.
Many developers will give up when they realize they have to learn both activiti cloud and keycloak. That's too heavy for them!
As a solution ,I think activiti cloud should remove the keycloak and write some authentication filters to implement standard
authentication protocols like oauth2 ,SAML for instead. And developers can config the oauth center information in yaml file.
Hi, I've spent 2 weeks to try activiti cloud v7.1.0.M6 and v7.6.0 with docker and run it successfully. I think the way to cloud is great. Embedded workflow will be eliminated in the future. However, I have some suggestions about activiti cloud. In the architect way, I think deep integration with keycloak is a bad choice.
Most of developers here just want a workflow solution which is easier to integrate with their existing user authentication system instead of a solution to rebuild their authentication system. Secondly, you can say that keycloak can work as an identity providers with any existing user authentication systems. But it will take more time for them to learn keycloak. Many developers will give up when they realize they have to learn both activiti cloud and keycloak. That's too heavy for them! As a solution ,I think activiti cloud should remove the keycloak and write some authentication filters to implement standard
authentication protocols like oauth2 ,SAML for instead. And developers can config the oauth center information in yaml file.
Thanks!