IFTTT vs. InterSystems Ensemble (legacy product)

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

• Best suited for fast development with a fundamental emphasis on object orientation
• Prohibitive costs for very small integration projects

• 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

• Easy to use: The simplicity of its programming language allows fast learning. Visual environment to generate complex code.
• Robust: A fall of the system will not be a problem. Never again will information of the transactions in progress be lost. Never more messages lost.
• Connect to the world: The most popular connection is possible to implement quickly. FTP, File folder, TCP, SMPT, REST.... all method are ready to use. Only define "where" and "how"

Incentivized

• 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

• Given that Ensemble and Cache are one of if not the only true fully object orientated database/development technologies for massive transactional data systems its customizability is extensive and it just comes down to the creativity of the developer to get the products to pretty much do whatever they want to do with it. However, this is not necessarily obvious to newcomers to the technology.
• The developer community could do with greater participation from the software developers/application specialists and engineers within InterSystems.
• More extensive documentation and greater access to proven working solutions particularly in the realm of some of the lesser known or new and upcoming technologies.

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

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

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.

I have yet to raise an issue with InterSystems WRC that they have been unable to resolve to my satisfaction in the 20+ years that I have worked with their products.

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

Incentivized

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

Mirth is another integration platform that we have used but its development, in Java, made us always create new methods every time a new product was integrated. Every connection process had to be developed from the beginning and it was not easy to reuse code. Nor did it allow us to have an extensive catalog of HL7 messaging, having to perform the validation of each and every one of its fields manually.

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

• We have integrated 5 laboratories in a treatment monitoring system in less than a month of development. Being able to integrate the following in a period no longer than a week.

Incentivized