Azure Functions enables users to execute event-driven serverless code functions with an end-to-end development experience.
$18
per month approximately
Camunda
Score 7.8 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 Functions
Camunda
Editions & Modules
No answers on this topic
Self-Managed Enterprise
Contact Sales
per year
SaaS Enterprise
Contact Sales
per year
Offerings
Pricing Offerings
Azure Functions
Camunda
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Azure Functions
Camunda
Features
Azure Functions
Camunda
Access Control and Security
Comparison of Access Control and Security features of Product A and Product B
They're great to embed logic and code in a medium-small, cloud-native application, but they can become quite limiting for complex, enterprise applications.
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.
They natively integrate with many triggers from other Azure services, like Blob Storage or Event Grid, which is super handy when creating cloud-native applications on Azure (data wrangling pipelines, business process automation, data ingestion for IoT, ...)
They natively support many common languages and frameworks, which makes them easily approachable by teams with a diverse background
They are cheap solutions for low-usage or "seasonal" applications that exhibits a recurring usage/non-usage pattern (batch processing, montly reports, ...)
My biggest complaint is that they promote a development model that tightly couples the infrastructure with the app logic. This can be fine in many scenarios, but it can take some time to build the right abstractions if you want to decouple you application from this deployment model. This is true at least using .NET functions.
In some points, they "leak" their abstraction and - from what I understood - they're actually based on the App Service/Web App "WebJob SDK" infrastructure. This makes sense, since they also share some legacy behavior from their ancestor.
For larger projects, their mixing of logic, code and infrastructure can become difficult to manage. In these situations, good App Services or brand new Container Apps could be a better fit.
This is the most straightforward and easy-to-implement server less solution. App Service is great, but it's designed for websites, and it cannot scale automatically as easily as Azure Functions. Container Apps is a robust and scalable choice, but they need much more planning, development and general work to implement. Container Instances are the same as Container Apps, but they are extremely more limited in termos of capacity. Kubernetes Service si the classic pod container on Azure, but it requires highly skilled professional, and there are not many scenario where it should be used, especially in smaller teams.
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.
They allowed me to create solutions with low TCO for the customer, which loves the result and the low price, that helped me create solutions for more clients in less time.
You can save up to 100% of your compute bill, if you stay under a certain tenant conditions.
The positive impact is that we are able to ensure the business process is being followed and that results in orders getting processed successfully leading to customer satisfaction and revenue
Another positive impact is that we are able to track any anomalies and any errors in the order flow and retry them so that users don't have a negative experience.
A negative point is that it is an overhead to maintain so there is significant engineering effort getting invested there
