We performed a comparison between Camunda and erwin Data Modeler by Quest based on real PeerSpot user reviews.
Find out in this report how the two Business Process Design solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."We are using the BPMN engine of Camunda; we are not using the user interface. We are using just the engine, the back end of this. For us, it is working quite well."
"Being able to use a Java-based solution makes the product flexible."
"We have the ability to modify the product if we need to, and that comes in handy whenever we need to add new functionality and features."
"The interface and the number of connectors that they provide are the most valuable features. The support here, it's kind of okay. But the main thing is with the number of connectors and the UI, the user interface."
"It allows me to present or to demonstrate the business process flow, visually, without having to resort to PowerPoint, Visio, or other products."
"When I compare it with other BPM tools, like IBM, it is great, open source, and free when you use the community version."
"The most valuable feature of Camunda Platform is its Microservices architecture, which is easily integrable with APIs."
"The flexibility characteristic in a BPMS, through BPMN and DMN, is undoubtedly the most interesting feature for our business."
"The product lets us import different types of models from various databases."
"Drag-and-drop data modeling and reverse engineering out of databases are the most valuable features of erwin Data Modeler by Quest."
"It supports a wide variety of databases, including the latest ones. We have chosen to go for a cloud-based database, and it supports that, which is very useful."
"The logical model gives developers, as well as the data modelers, an understanding of exactly how each object interacts with the others, whether a one-to-many, many-to-many, many-to-one, etc."
"The product allows us to reuse entities and attributes."
"The solution is excellent in providing a visual representation of a database and can generate DDL for implementing changes. We use DDL for logical purposes to review with business people, ensuring they have the required fields for processing. We also use it as a data dictionary for the physical data model to understand all the purposes of the terms. This helps us map the logical and physical terms with the business definition to understand our data."
"We use the macros with naming standards patterns, domains, datatypes, and some common attributes. As far as other automations, a feature of the Bulk Editor is mass updates. When it sees something is nonstandard or inaccurate, it will export the better data out. Then, I can easily see which entities and attributes are not inline or standard. I can easily make changes to what was uploaded to the Bulk Editor. When taking on a new project, it can save you about a half a day on a big project across an entire team."
"The most valuable features are being able to visualize the data in the diagrams and transform those diagrams into physical database deployments. These features help, specifically, to integrate the data. When the source data is accumulated and modeled, the target model is in erwin and it helps resolve the data integration patterns that are required to map the data to accommodate a model."
"As we experienced some difficulties in the beginning, deployment took almost a month."
"I would also like a very easy to use form builder."
"The GUI needs to be improved, with more configuration options."
"I would like to have a feature for audit logging, audit logs and audit log management. And some history of use for the audit logs."
"It has a Postgres database at the backend, and it is very difficult to scale if you increase the number of processes running. We did hit some barriers. We were able to overcome them, but it was a problem. Camunda has another product called Camunda Cloud, which supposedly doesn't have the same scalability problems, but we are not using Camunda Cloud because the set of features is smaller than Camunda On-Premises. So, its scalability can be improved. Because it has a single database, it is more difficult to scale if you have a huge success."
"If Camunda could develop something that creates user forms that would be a great feature to have. They also need to improve the UI."
"It lacks some preset features and configurations which would make it more plug-and-play for customers."
"If they could build some scripts or some configuration to get it up and running in a Docker environment, that would be good. I didn't find anything when on Docker, however, maybe they have something and I didn't see it yet."
"I still use Visio for conceptual modeling, and that's mainly because it is easier to change things, and you can relax some of the rules. DM's eventual target is a database, which means you actually have to dot all the Is and cross all the Ts, but in a conceptual model, you don't often know what you're working with. So, that's probably a constraint with erwin. They have made it a lot easier, and they've done a lot, but there is probably still room for improvement in terms of the ease of presentation back to the business. I'm comparing it with something like Visio where you can change colors on a box, change the text color and that sort of stuff, and change the lines. Such things are a whole lot easier in Visio, but once you get a theme organized in erwin, you can apply that theme to all of the objects. So, it becomes easier, but you do have to set up that theme."
"It is not a very stable solution. I rate the stability five out of ten."
"erwin generally fails to successfully reverse engineer our Oracle Databases into erwin data models. The way that they are engineered on our side, the syntax is correct from an Oracle perspective, but it seems to be very difficult for erwin to interpret. What I end up doing is using Oracle Data Modeler to reverse engineer into the Oracle data model, then forward engineer the DDL into an Oracle syntax, and importing that DDL into erwin in order to successfully bring in most of the information from our physical data models. That is a bit of a challenge."
"I would like the solution to be more user-friendly to deploy."
"I find the UI very clunky and very difficult to use. If I add columns to a table the whole workflow could be so much easier. I get frustrated using it. I've tried other tools. I've tried to get off of erwin a few times. I always come back to it because every tool has its own set of problems, and it seems like if I have to pick my poison, I stay with erwin. But so many things that are clunky with it."
"It does not have a cloud application."
"The solution's reporting side needs to be improved."
"We can only get licenses through partners."
Camunda is ranked 2nd in Business Process Design with 69 reviews while erwin Data Modeler by Quest is ranked 9th in Business Process Design with 37 reviews. Camunda is rated 8.2, while erwin Data Modeler by Quest is rated 8.6. The top reviewer of Camunda writes "Open-source, easy to define new processes, and easy to transition to new business process definitions". On the other hand, the top reviewer of erwin Data Modeler by Quest writes "The product lets users import different types of models, but it is expensive, and the interface must be improved". Camunda is most compared with Apache Airflow, Bizagi, Pega BPM, IBM BPM and Appian, whereas erwin Data Modeler by Quest is most compared with SAP PowerDesigner, IDERA ER/Studio, Visio, Lucidchart and Sparx Systems Enterprise Architect. See our Camunda vs. erwin Data Modeler by Quest report.
See our list of best Business Process Design vendors.
We monitor all Business Process Design reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
