Minute 1
Register for Camunda Cloud. Fill out the registration form and confirm your email address.
Minute 2
Log in to the cloud console and create your first cluster. Jump to the cluster details by clicking on the cluster.
Minute 3
Create an API client: this is necessary to communicate with your cluster. You can see it as a key to your cluster. Without this key the door to your cluster will remain closed. Once you have created your client, you will see a dialog with your credentials. You also have the possibility to download a file that contains export statements. This file is the easiest way, because it bundles all information in one file.
Minute 4
Log in to Restzeebe. You can answer a few questions about yourself that will help make the product better and then you’re ready to go.
Minute 5
Import the created client. When you have just downloaded the file, you can enter the entire content into the input field. The necessary information will then be extracted. Alternatively, you can enter all the necessary data one by one: ClusterId, ClientId and ClientSecret. With the import you have successfully completed the first achievement of Restzeebe.
Minute 6
In the next step you interact with your cluster for the first time. Get the status of your cluster. If this action is successful, you have communicated with your cluster for the first time. So far it was relatively boring - you have so to speak given a ping and received a pong.
Minutes 7 to 10
Now comes the exciting part :) Deploy the first model. Restzeebe deploys a simple first workflow consisting of a start and end event. In between there is an intermediate message event. This means that a started instance waits in the message node until a message arrives that matches the configured parameters. Open Operate (the link is highlighted) to see your workflows (and instances). Since you have only deployed one workflow so far you will only see this entry on the dashboard. Now start a new instance. Basically you can start any workflow with Restzeebe. You only need the BPMN Process Id. Since you have deployed the workflow described above it makes sense to start a new instance. The BPMN Process Id of the workflow can be found in the response of the deployment. You have to enter this Id in the input field. If you now jump back to Operate and refresh the page you will see an active instance. This instance is waiting in the message node. In the last step you can now send a message to your cluster. In the description of the action you will find an icon that prepopulates the input fields. Send the message and switch back to Operate. The instance should now be finished. Congratulations, you have executed your first workflow in the cloud!
Isn’t that a bit too easy?
Admittedly it is a very simple workflow. Maybe you are thinking now: Whoa, seriously? I wasted 20 minutes of my life for this? I can only tell you: this is just the beginning. It is your Hello World process. As described at the beginning, everything is a process. It is certainly not reasonable to model a workflow for every use case and let it run through a workflow engine. But: there are enough examples where it makes more than sense. I would like to finish this article with spaghetti. Can’t the spaghetti effect occur quickly as well when I design and execute processes? And the answer is very clear: yes. But the big difference from my point of view is that it is clearly visible. And that quickly leads to headaches ;) I hope you did not expect an alternative recipe that plays in the league of Spaghetti Bolognese ;)