IBM App Connect vs. IFTTT

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.

Incentivized

Because of the multitude of options with IFTTT, it is hard to describe the best use scenarios, but I will share how I use the platform at this time. I use IFTTT to check Craigslist for certain IT equipment postings and email me if that occurs, turning items on and off with geo-fencing and WiFi network presence, and linking my calendar to my to-do list

Incentivized

• Just the ability to display and consume data through a single dashboard makes this a great application for our business purposes.
• With the ability to consume their exposed API, data validation and manipulation becomes a breeze.

Incentivized

• IFTTT manages a number of social media accounts quite well. Being able to login to one platform with access to all your accounts is great.
• IFTTT is easy to set up. IFTTT has a number of crowd sourced and created formulas that you can use, or if you're looking for something specific you can create your own. This allows for an endless number of combinations and ways to engage with the program.
• IFTTT doesn't require constant upkeep. Once you have things setup you can forget about it and it just works.

Incentivized

• modernization made easy, when a modernized project is created by importing a java code.
• more pre-built connectors
• watsonx code assistance for ESQL capability.

• The website section "Activity" tends to get very crowded over time. It would benefit from some search and filter functionalities.
• Some services lack ingredients. "Ingredients" are attributes passed from one service to another to enhance IFTTT's power. However, some services (like Evernote's notes, for example) currently have too few ingredients available.
• It is not possible to link more than two services. It would be great, for example, to have an option to take a mail message and post in multiple social networks and blogs with the same applet.

Incentivized

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.

Incentivized

There is no better alternative and although Integromat is new and the GUI is slick, they make you pay per push and IFTTT does not. The rest of the competition make you pay per integration or are just not as seamless in usage or have the depth of catalogue. If you use Zapier for instance, it is because they have an integration you have to use, not because Zapier does a better job.

Incentivized

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.

Incentivized

For the most part, IFTTT is great but it does have its limitations. You may only do one thing at a time. If you want branching logic it can be cumbersome and clunky. This it where something like Microsoft Flow does better. For simplicity, nothing can beat IFTTT for how easy it is to set up and use right out of the box

Incentivized

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.

Incentivized

I have had a few issues with apps over the years. Compared to other services, ITFFF is the best choice but no service is perfect unless you build it yourself for yourself. ITFFF needs more tutorials on how to create a custom platform, but overall I will recommend it as an easy to use, time-saving service.

Just try it for your own social media platforms. Then imagine how much money it can save/make.

Incentivized

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.

I haven't used Zapier extensively, but it seems that IFTTT is much simpler to set up. However, Zapier appears to be a much deeper integration where you can sync a variety of fields of data and customize the sync more than you can with IFTTT. Zapier may be more valuable for someone with a complex need and IFTTT is built for simple solutions for more basic apps.

Incentivized

• 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.

Incentivized

• We have not had to purchase a subscription to a social media automation tool.
• We have saved time sharing information between systems.
• We have been able to reach out to our clients faster because notifications are coming to our attention in more ways than just our inbox.

Incentivized