Microsoft offers the Azure Logic Apps as a cloud-based integration service, supporting data and application integration.
$0
per execution
IBM App Connect
Score 9.3 out of 10
N/A
IBM’s App Connect is a cloud-based data integration platform with data mapping and transformation capabilities within connectors between high-volume systems. App Connect also offers near-real time data synchronization and an API builder that is adaptable to the user’s coding skill level.
N/A
Pricing
Azure Logic Apps
IBM App Connect
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
No answers on this topic
Offerings
Pricing Offerings
Azure Logic Apps
IBM App Connect
Free Trial
Yes
Yes
Free/Freemium Version
No
No
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
IBM App Connect
Features
Azure Logic Apps
IBM App Connect
Cloud Data Integration
Comparison of Cloud Data Integration features of Product A and Product B
Microsoft Azure Logic Apps was a perfect solution for us to integrate the apps and products we used in our business to create automated workflows which were also complex and very advanced. This was a very new feature for us, and also it reduced our software costs massively and also saved us a lot of time. With the crisis, we were in back then Azure turned out to be the best cost-friendly solution because we only had to pay for what we used!
IBM App Connect Enterprise is well-suited for high-volume enterprise systems that demand robust scalability and high reliability. It excels at hybrid connectivity by easily integrating various on-premises systems using its extensive catalog of connectors. It is also ideal for workflows that require a balance between efficient low-code and the incorporation of complex, custom Java logic. On the other hand, the platform is less appropriate in scenarios requiring high development autonomy, as installation and configuration at the server level is excessively complex, creating a strong dependency on other infrastructure teams. It is also not ideal if detailed traceability and monitoring of workflows must be seamlessly managed within the tool itself, as this is difficult to manage directly in ACE. IBM App Connect Enterprise está bien adaptado para sistemas empresariales de alto volumen que exigen una escalabilidad robusta y alta confiabilidad. Sobresale en la conectividad híbrida al integrar fácilmente diversos sistemas locales (on-premises) utilizando su amplio catálogo de conectores. Además, es ideal para flujos que requieren un equilibrio entre el low-code eficiente y la incorporación de lógica Java compleja y personalizada. Por otro lado, la plataforma es menos apropiada en escenarios donde se requiere una alta autonomía de desarrollo, debido a que la instalación y configuración a nivel de servidor es excesivamente compleja , lo cual crea una fuerte dependencia de otros equipos de infraestructura. Tampoco es ideal si la trazabilidad detallada y el monitoreo de los flujos deben gestionarse sin problemas dentro de la propia herramienta, ya que esto resulta difícil de manejar directamente en ACE. Parts of this review were originally written in Spanish and have been translated into English using a third-party translation tool. While we strive for accuracy, some nuances or meanings may not be perfectly captured.
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.
It is the best on-premise application to cloud integration in the market. I guess IBM is planning to integrate IBM App Connect with the IBM API Connect solution.
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.
You can do some really powerful things with this system. The overall design is an attempt to make configurable some of the routine tasks/common functionality, but allow for development/customization of the core of the application.
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.
Usually, the IBM Ops team provides a resolution or a response for 80% of defects raised in my project. There is one which has been open on their end for more than 3 months. With literally no response even after multiple follow-ups.
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 and use is by far the most popular.
IBM App Connect started as MQSeries Integrator (MQSI) more than 20 years ago. In the IT environment, this is like an eternity. And this allowed a lot of customer experience and needs to be embedded in the product. Without it becoming a legacy application. The changes done in the latest version are preparing it for a Cloud/containers world without losing the previously learned knowledge.
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.
We never implemented Cast Iron in production. When compared to five competing products in the iPaaS space it didn't make it past the first few test scenarios we threw at it.