Message brokering across different systems, with transactionality and the ability to have fine tuned control over what happens using Java (or other languages), instead of a heavy, proprietary languages. One situation that it doesn't fit very well (as far as I have experienced) is when your workflow requires significant data mapping. While possible when using Java tooling, some other visual data mapping tools in other integration frameworks are easier to work with.
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)
Some of the documentation is a little sparse. In particular, its TCP-based routes use an underlying Netty server, and the interactions between Netty's decoder capabilities and Apache Camel's routing/handler capabilities can be a little muddy at times. In general it is clear which routes and endpoints are the more frequently used and which haven't been given as much attention.
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.
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.
Apache Camel has been the integration framework of choice, but I was not the person to make the decision to use it. Compared to other competing products like Tibco Business Works, etc., it is free and open source and its licensing policy is acceptable to the management of Cox.
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!
Very fast time to market in that so many components are available to use immediately.
Error handling mechanisms and patterns of practice are robust and easy to use which in turn has made our application more robust from the start, so fewer bugs.
However, testing and debugging routes is more challenging than working is standard Java so that takes more time (less time than writing the components from scratch).
Most people don't know Camel coming in and many junior developers find it overwhelming and are not enthusiastic to learn it. So finding people that want to develop/maintain it is a challenge.
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.
