holunda-io / camunda-bpm-cloud

Discontinued, look for camunda-bpm-taskpool
https://github.com/holunda-io/camunda-bpm-taskpool
Apache License 2.0
19 stars 0 forks source link

what is the state of camunda-bpm-cloud? #55

Open akoranne opened 6 years ago

akoranne commented 6 years ago

For a client of mine, we are looking into Camunda. We want to run Camunda on a cloud in cloud native approach.

The "camunda.com" site is not clear on the cloud native aspects of Camunda. I was able to get the docker image running on Kubernetes. But not sure how scaling will impact it.

what is the state of camunda-bpm-cloud? I see only one release and that was back in 2016. Is this initiative dormant? Is Camunda.com championing the cloud native transformation?

Can someone help me get some understanding on this?

jangalinski commented 6 years ago

Hello Ajay, thanks for taking interest in our project. The title of this repo might be a bit misleading ... we are aiming for a framework/blueprint that allows you to run multiple process engines and have them share a global tasklist, so all human workflows are accessed via the same UI. Of course this is of great relevance when you run multiple engines in "the cloud", but we just provide the necessary tools and ideas, this repo is not indended to work with any particular cloud platform ... in fact, on the master branch we just use docker-compose to get all required modules up and running, but thats not very "cloudy" ... there is a branch that adopts the approach for pivotals cloud foundry, though, which already prooved itself in a clients project.

State: we had two goals when we set this up: understand how 12factor/cqrs/camunda/"cloud" (in the sense of distributed engines) behave and provide a community extension that allows you to adapt the ideas to your custom cloud provider as easy as possible.

To be honest, since we spent the last month implementing the approach in cloudfoundry/closed source, the state of this repo is somewhat undefined ... after discussing with camunda, we found that the example application setup with edge/configuration/registry/docker/rabbit/.... is too complicated to serve as a simple example and adopting to a special cloud provider like cloudfoundry limits the usability for all other platforms. But thanks for pinging, I guess this will force us to discuss how to continue.

From what you mentioned ("docker container with camunda in kubernetes") I would guess that you do not need this at the moment, it might get relevant once you decide to deploy a global tasklist. If you just want to scale camunda applications in kubernetes, have a look at the clustering model: https://docs.camunda.org/stable/guides/user-guide/#introduction-architecture-overview-clustering-model - let all your camunda nodes share a relational db, and you are good to go.

Hope that helps, Jan

akoranne commented 6 years ago

Jan, Thank you for your reply. You mentioned we spent the last month implementing the approach in cloudfoundry/closed source. That is good news. My client is very interested in it. My client would prefer we go on cloud foundry for Camunda.

We have a meeting scheduled for today with your sales team. I will bring them up to speed with this conversation.

Connect with me on LinkedIn and we can discuss more.

Thank you, --ajay