Microsoft offers the Azure Logic Apps as a cloud-based integration service, supporting data and application integration.
$0
per execution
Camunda
Score 7.9 out of 10
N/A
Camunda is a process orchestration tool designed to help organizations design, automate, and improve any process. Built for business and IT collaboration using BPMN and DMN standards, Camunda aims to enable seamless integration across endpoints to transform mission-critical processes.
N/A
Pricing
Azure Logic Apps
Camunda
Editions & Modules
Actions
$0.000025
per execution
Standard Connector
$0.000025
per execution
Enterprise Connector
$0.001
per execution
Integration Account - Basic
$0.42
per hour
Integration Account - Standard
$1.37
per hour
Self-Managed Enterprise
Contact Sales
per year
SaaS Enterprise
Contact Sales
per year
Offerings
Pricing Offerings
Azure Logic Apps
Camunda
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Azure Logic Apps
Camunda
Considered Both Products
Azure Logic Apps
Verified User
Anonymous
Chose Azure Logic Apps
The other tools which we have been using do not suite well to integrate other systems (online and onprem) and also other azure services. This tool provide lot of prebuilt connectors that helps us to use the functions within the workflows. This tool is well suited for technical …
Other services can, on some level, offer some type of subscriber/publisher pattern. For example, you could have an Azure Function watch for changes to a database and then sync the data to Cosmos DB. However, with a few clicks, Logic Apps can easily handle the task without …
This is very dependent on the line of work you are in and the unique company requirements, as is the case with everything. We utilize Azure Logic Apps for all of our computing solutions within our domain, and it has always worked flawlessly. One of the simplest clouds to set up …
Honestly, both are robust applications that have helped our business. Amazon had more help training and help resources and allowed us to hit the ground running a little easier. However, it seems like Azure is a more complete option that has more overall resources that our …
When we proposed products for central integration, we were also introduced to software like Pabbly - which was in its early stages of company growth. The main reason why we picked Azure Logic apps over the other software is that it is manufactured by the renowned company …
They are both good, but for our current moment, having Azure was a better decision. Hubspot has prices in dollar and Brazilian currency is not well at the moment, so we needed to make a decision.
Like all things, this is very much based on the line of work you are in and the specific business needs. We use Azure for our computing solutions under our domain, and it works great every time! By far one of the easiest clouds to get up and running.
There are some logic that are too complex to be executed in Azure Logic Apps. It's a smart choice to execute them in Azure Functions. Azure Logic Apps has an OOB connector to connect to Azure functions. The authentication part is taken care of by MSI (so nothing needs to be …
Microsoft Logic Apps is much more enterprise-ready. With our company being more invested in Microsoft, this was a no brainer for us to leverage the tool. Its ease of use and scalability makes it a good choice for an enterprise workload.
Azure Logic Apps has its positives and negatives. We have found that solely relying on it it not a best practice. But that Azure Logic Apps shine when used in concert of the other offerings out there as a part of the whole solution. There are tasks that Azure Logic Apps …
They're just different products with different target audiences. In different ways, IBM and Pega have offerings that are meant to serve processes in a platform-centric approach to their customers. An emphasis on unified development environments, including forms building, …
Lacks good documentation. Training and documentation is geared towards those who are already technically adept. Does not have as many data integrations as other full fledged products. Paid version of Camunda is not as fully fledged as other products.
1. For simple tasks / moderately difficult tasks (where there are not too many condition checks) 2. We have less time for development, and the Agenda is simple. 3. Avoid Azure Logic Apps when you are unsure about hitting the limits (check latest limitations of Azure Logic Apps in MS docs)
Camunda Platform is well suited for scenarios where there are different stages in a business flow and the flow is driven by user action at each stage. For example placing of an order on an ecommerce platform. Depending on whether user was able to make the payment or not the workflow would go to dispatch or retry stage. Now the retry stage would trigger further actions like sending follow up emails etc. Likewise, dispatch stage would have a different set of actions. Since every order is important and we need to know where it stands, using Camunda Platform is imperative. Camunda Platform might not be a right choice where just a one off thing needs to be done. For example, uploading of product information by user or periodic processing of heavy images by a worker. These are all either one step processes or periodic automated processes where we can track the status without using a business modeler like Camunda Platform.
Microsoft Azure should be unclouded with its pricing. We don't always know how much an inclusion will affect the monthly price. So we have to speculate where we are with the price and if we can afford to include another asset.
Documentation - It is usually daunting for beginners because of lack of good documentation
Simplified setup on local machine for Camunda Server would help developers test changes quickly
Easier migration from one deployment version of a Camunda process to another deployment version would help in making changes and deploying them faster.
Heap memory management becomes issue at times resulting in stuck processes. This needs to be resolved.
I found them easy to use and adapt to different scenarios, from Azure management to link processes between REST APIs. Together with Function Apps, they're probably the most useful resource type for Azure. Today, I use them in production, and that's a key component: stable, secure, easy to manage, and maintain.
Azure Logic Apps are backed by Azure and Microsoft. There is a wealth of information on the internet about both of these platforms. In addition to this Microsoft has a huge bush to using this platform and have offered many solutions and support options to the user. The only drawback is that it is a fairly new platform so the 3rd party information tends to be lacking.
When we proposed products for central integration, we were also introduced to software like Pabbly - which was in its early stages of company growth. The main reason why we picked Azure Logic apps over the other software is that it is manufactured by the renowned company Microsoft and we had nothing to worry about our data security. Also, Logic apps offered a great deal when it came to pricing and it was also so much easier to negotiate the plans and prices with the customer care representatives at Azure Logic Apps!
Moving to Serverless Computing obviously makes the organization get rid of dependent Infra.
ROI can be seen immediately as the required infra can be decommissioned after a successful quarter run.
Being deployed as a single entity or single app on Azure Logic Apps, Organizations need to be more careful with controls applied to meet compliance and security posture.