Our primary use of ECS is to host all our services in the cloud. We work in the legal sector, and our workloads are often deployed on Fargate containers or Azure containers to abstract the hardware.
Camunda
CamundaExternal reviews
External reviews are not included in the AWS star rating for the product.
Product Owner Banking Industrie
A Robust Platform for Workflow and Process Automation
Great process orchestration tool
Standardization thanks to orchestration with Camunda
Orchestration made simple
Review of Process Orchestration
Camunda: A platform that helps businesses automate and manage complex processes.
Review for the software
Reduces costs with hardware abstraction and simplifies scaling
What is our primary use case?
What is most valuable?
EC2 makes scaling horizontally incredibly easy, especially when working under the ECS service. Nowadays, I almost never need to create instances of virtual machines because most workloads can be deployed on Fargate containers. This abstraction of hardware reduces the need to think about it.
My costs are reduced. Working with ECS and Fargate doesn't require saving processing units for idle services. Previously, using EC2 required keeping entire virtual machines running, however, Fargate eliminates this cost. ECS also allows for horizontal scalability with thresholds that can be configured for CPU or memory.
What needs improvement?
There is an issue where, in some situations, I need to scale up by observing both CPU and memory usage of containers, yet under the current options available at Amazon, this is not possible. I have to choose between monitoring CPU or memory to scale my solution. Not every software is built for deployment as a container service, although the current architecture trend is changing this.
For how long have I used the solution?
I host everything in the cloud, and I have over ten years of experience. I use EC2 as a hosting technology and have been using it for a long time.
What do I think about the stability of the solution?
My services running on ECS are also on Azure Container Service. I have never experienced any flicker or downtime. These are highly available services. It's very stable.
What do I think about the scalability of the solution?
ECS and Fargate make horizontal scalability very easy. I rate the scalability a ten out of ten. It allows for easy scaling, especially with ECS service configurations.
How are customer service and support?
The AWS Support is incredible. They always invite us for meetings to showcase new solutions. I have a very good relationship with AWS, Microsoft, and GCP for support. AWS provides the best support, followed by Microsoft, and then Google.
How would you rate customer service and support?
Positive
How was the initial setup?
Setting up ECS is simple, although there are some tricks involved. I usually have to define private and public networks and bind all related services. It's easy but not super straightforward. I had to repeat the process two or three times before I could teach others how to configure it.
What was our ROI?
Hosting services on Fargate reduces our processing costs since we don't need to keep virtual machines running for workloads anymore. This results in cost reductions.
What's my experience with pricing, setup cost, and licensing?
AWS pricing is very competitive compared to Azure and cheap compared to Google. For some services, such as hosting databases, Google is really expensive.
What other advice do I have?
On a scale of one to ten, I rate ECS a ten out of ten. It's an incredible service, and I prefer it over Kubernetes. I suggest checking the integration of software for deployment in a serverless environment. Some software can be challenging to deliver this way.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Allows for quick process design and implementation
What is our primary use case?
Camunda can be used in various workflow scenarios, such as policy administration systems, onboarding, account management in telecom, insurance products, policy issuance, claims management, and loan management.
It is also suitable for customer service center activities where customers' accounts are created. Camunda can manage any workflow that requires customer interaction with the system. It is a competitor to other BPM solutions like Pega.
What is most valuable?
The architectural part of Camunda for workflow design is highly valuable, especially the Camunda Modeler, which allows quick process design and implementation. Camunda's DML is a competitor to the implementation of business rules.
It integrates well with Java, making it suitable for various technology stacks. Camunda facilitates microservices integration. Its SaaS model provides scalability, automatically managing and scaling implementations.
What needs improvement?
The deployment model could be improved for easier implementation. More open documentation would be beneficial to understand the deployment process better and facilitate easier setup.
For how long have I used the solution?
I began working with Camunda in 2013.
What do I think about the stability of the solution?
Camunda is quite stable, and I would rate its stability around eight to nine out of ten. There haven't been any significant outages in my experience with Camunda.
What do I think about the scalability of the solution?
Camunda offers a high level of scalability, especially when using its SaaS model, which manages and scales implementations automatically. I would rate its scalability a ten out of ten.
How are customer service and support?
Camunda's community is medium-sized, offering reasonable support. However, they provide better support for the enterprise edition. There was not a large community in the early years.
Which solution did I use previously and why did I switch?
Other competing solutions include JBPM, Activiti, and Pegasystems.
How was the initial setup?
The initial setup can be difficult, with a rating of seven on a scale from one to ten. While not very hard, some features present challenges.
What about the implementation team?
For earlier versions, implementation involved bundling applications as WAR or EAR files using Maven, and deploying them on JBoss Server. I have yet to explore Camunda 8's implementation process.
What's my experience with pricing, setup cost, and licensing?
There is a licensing cost for using the SaaS model and Enterprise edition of Camunda, although I am not aware of the specific pricing.
Which other solutions did I evaluate?
Other solutions evaluated include JBPM and Activiti.
What other advice do I have?
For anyone considering using Camunda, it is essential to understand your workflow clearly. Camunda is the best among similar solutions like JBPM and Activiti. I love working with Camunda.