Camunda can be used as a cloud service to implement applications using various programming languages like Java, JavaScript/NodeJS, and Scala. The Camunda engine runs in the cloud and processes can be deployed to it. Services can run both on-premise and in the cloud. Tasks from cloud processes are invoked via REST/SOAP calls to on-premise services. This architecture provides better decoupling of the engine and services, allowing them to be scaled independently. It also gives services more autonomy over their work.

1. How can I use Camunda as Cloud Service and implement my
Applications using arbitrary Programming Languages like Java,
Javascript/NodeJS or Scala?
Daniel Meyer @meyerdan

2. This
is the
Cloud
(Docker Swarm @
Camunda HQ)

3. Camunda Engine runs in the Cloud and
the following BPMN Process is deployed

4. This is
On Premise
(my Notebook)

5. The services run on premise
The services are implemented
using different technologies.

6. Lets execute that process
Cloud
Process Engine
On Premise
Services

7. <Live Hacksession>

8. Task
Task
Task Task
Task
Task
Service
/ Application
Service Service
On Premise
Topic
publish
subscribe
Cloud
How does it work?

9. Task
Task
Task Task
Task
Task
Service
/ Application
invoke
SOAP / REST
Service
/ Application
SOAP / REST
Service
/ Application
Messaging
system
+ Monitoring,
+ Error Management
+ ...
Security?
Data Mapping?
Service Registry?
Service Unavailable?
…?
Wouldn’t this work too?

10. 1. Use Camunda comfortably from arbitrary Programming Languages
(Python, C#, Javascript / NodeJS, … as easy to use as Java)
2. Hybrid On-Premise / Cloud Workflows
(Camunda runs in the läuft in the Cloud, Systems in the Cloud and on Premise)
Vorteile dieser ArchitekturNew Possibilities

11. Vorteile dieser Architektur
1. Better Decoupling Engine <> Services (Apps)
a. Start / stop Engine independently from Services
b. Scale Engine / Services independently from each other
c. Engine does not need to know anything about the sServices
2. Greater Autonomy of Services (Apps)
a. Service decides what kind of work it performs
b. Service decides when it performs the work
c. Service decides how much work it performs and at which rate
=> Microservice Ideas
Advantages

12. And all of this without complex
infrastructure!!!
Message Bus, ESB, Service Registry, Data
Mapping, Web Services, Stomach Pain,
Headaches, Sleepless nights, Divorce, Suicide.

13. Brought to you by Camunda
Philipp Ossler
Nico Rehwaldt
Daniel Meyer