New to the tool; excited to learn more
What do you like best about the product?
From what I've seen at CamundaCon, it is a powerful tool for agentic automation. I like the flexibility it offers and seemingly low effort onboarding
What do you dislike about the product?
I would need more experience with the tool to know what I dislike.
What problems is the product solving and how is that benefiting you?
We have not yet implemented a Camunda solution
Good orchestration software
What do you like best about the product?
Good orchestration software but upgrading is expensive
What do you dislike about the product?
upgrading is expensive and seems cumbersome
What problems is the product solving and how is that benefiting you?
Business use cases specific to our area
Supports long-running asynchronous processes effectively but has not evolved much in recent years
What is our primary use case?
We leverage Camunda for two different use cases in Santander Brazil. I used and we used to have an orchestration flow for processing new credit approvals. Once the customer requested a new credit on the Santander mobile app, they received the confirmation instantly, online, but asynchronously, we had several updates and documentation to prepare in order to make back-office processes complete. The customer received the instant confirmation, but we used to have a long-running process with several steps running in parallel and asynchronously, and those steps were orchestrated through Camunda. That was one use case, basically API orchestration in an asynchronous process with no human interaction.
We leveraged Camunda for the back-office processes for Santander Esfera, which is a loyalty program from Santander in Brazil. It is mainly a marketplace where customers can use loyalty points to redeem products. The order management process for that marketplace used to run through Camunda as well, leveraging APIs and in some cases, handling exceptions and human interaction.
What is most valuable?
Camunda's support for BPMN 2.0 is a great advantage because it allows us to have a common language to discuss technology and business in the same perspective. This capability used to allow us to anticipate issues and discussions with the business and product teams.
Since they are basically a fork from Activiti, which was a lightweight architecture that would allow us to run the process in a way we used to call the process API or a headless process. There was no need to deploy and run heavy and large tools and frameworks and middlewares, allowing us to embed the process engine inside our Java applications. That was another advantage, and it worked fairly well with cloud environments. The limitation they have with transactional databases that ultimately they were able to get rid of when they launched Zeebe was not really an issue for us. We did not have the scale and transaction volume that would make a need for such a high throughput environment. The standard or original Camunda deployment with a transactional database was more than enough for our use cases.
The learning curve for understanding how it works and deploying the first processes, especially for those people who have a background in Java, seemed to be a really fast-paced adoption for us. When we compared with other process automation tools such as Pega and IBM BPM, Camunda seemed a better approach for us.
What needs improvement?
I think Camunda is focusing too much on the SaaS offering right now and not much on improving and developing the product itself. I did not see any innovations on that aspect, especially for the open-source version. I was making some tests recently and the tool seemed pretty much the same as it was three or four years ago.
Since they made the move to cloud deployment in a more SaaS-oriented way, they do not invest too much in the community version. To be honest, it did not change much from the Activiti initial version. Activiti was pretty much what Camunda is today. They invested a lot on Zeebe and made it the engine for their SaaS cloud version. Camunda itself, the embedded engine, did not evolve too much. They could invest more on that.
What do I think about the stability of the solution?
With Camunda they have a tool called Cockpit. We measured the time for each step individually because each activity in the process was an API call to an external API in a different legacy system. We used to track the performance and other metrics on those specifically. We were not really concerned about the performance on the process itself because it was super simple, super straightforward, and it did not present itself as a bottleneck, nor did we feel it was adding additional time in the execution. For us, the process itself was fairly seamless.
What do I think about the scalability of the solution?
Camunda integrates well. They have that REST layer, REST APIs layer that makes it easy to integrate and make it part of a microservices ecosystem and APIs. That worked pretty well. We had some specific processes that were API orchestration processes, and the starting of the process was an API call directly through the Camunda engine. It played fairly seamless with no big issues on that deployment.
How are customer service and support?
The support for Camunda is great. The team is very responsive. They really understand deeply and in detailed fashion the solution. Any issue you have, they answer back right away. For the support, they made a great job. On a scale of 1 to 10, I would rate them a 10 for support.
How would you rate customer service and support?
What other advice do I have?
We purchased the license for Camunda. It was not simple, and at the end of the day, it is an expensive tool. I think for enterprises, it pays itself pretty well, but for startups and teams that are trying to make some tests and understand if the tool is the best solution for their specific scenarios, the pricing model right now is a concern.
I could not even purchase a version straight from their portal. I had to contact sales and then fill out a form, a representative team in Brazil received the form but did not get in touch. It is not really self-service, and I would prefer to have something where you can just put your credit card and use the tool as you want. That lack of transparency is an issue for us right now.
When we compared Camunda to other options for running back-office processes at Santander Brazil, those credit processes have very large profit margins. So any tool running on those processes would be of good return. When compared to Pega and IBM, we made the bet for the cost of development. With IBM specifically, we had the license already because we had other tools and contracts. But the development was not as straightforward, and the running infrastructure costs for running and setting up the tool was not cheap. It was more expensive than running the process embedded in our Java applications, the way we did with Camunda. For the total cost of ownership, Camunda seemed to be the best option, but it is not cheap.
I would rate Camunda a 7 out of 10. It is a great tool with great support, though licensing is not so good, and evolution-wise, they are not investing as much as they should. I do not think Zeebe is a no-brainer evolution for Camunda as the two products are very different.
New tool worth exploring
What do you like best about the product?
I think the ease with which we can orchestrate agents is amazing
What do you dislike about the product?
Nothing really I think the product is doing great
What problems is the product solving and how is that benefiting you?
Creating poc and trying it out
Working happily with camunda for 10 years noe
What do you like best about the product?
Developer friendly of the product camunda
What do you dislike about the product?
End of community version 7 is too fast to migrate all
What problems is the product solving and how is that benefiting you?
End 2 end processes, and monitoring them
Very good first experience at CamundaCon
What do you like best about the product?
Powerful but also simple to use and business oriented
What do you dislike about the product?
In terms of architecture and technicity it can be a challenge and need high level of skill for the teams
What problems is the product solving and how is that benefiting you?
Easy to create valuable use case
Alright event with ups and downs
What do you like best about the product?
Developer-friendlyness, good community with Mostar cery responsive people that like to help, mostly very detailled documentatuon
What do you dislike about the product?
Its very expensive for smaller companies that would like automate their processes but cant afford it
What problems is the product solving and how is that benefiting you?
Automating processes thst are mostly done manually
Review
What do you like best about the product?
The ease of setting up a process. And the speed of it.
What do you dislike about the product?
The forms can be a bit annoying to work with.
What problems is the product solving and how is that benefiting you?
It's let's me orchestrate complex processes
Flexible and powerful
What do you like best about the product?
Vert flexible and simple to implement use case
What do you dislike about the product?
I am exploring different use case and I found it is very easy to integrate.
What problems is the product solving and how is that benefiting you?
Banking use case
Great orchistrator
What do you like best about the product?
A good tool to do business orchastration
What do you dislike about the product?
Setting up self managed takes some time on openshift
What problems is the product solving and how is that benefiting you?
Process Management
