Ventajas e inconvenientes de los plugins de integración

Seleccionar la solución de software adecuada para la integración de datos puede ser complicado, con tantas opciones diferentes disponibles. Además, estas opciones le ofrecen sitios web, catálogos y folletos, que sólo le cuentan la mitad de la historia. Por esa misma razón, hemos trabajado para recopilar varias plataformas de integración de datos conocidas y menos conocidas en un documento único y fácil de leer para ayudarle en su toma de decisiones. En este blog, analizaremos los pros y los contras de la integración de plugins.

‍

Suppliers of renowned solutions, like Salesforce, Microsoft, Adobe, and so on, often offer small integration solutions based on plugins. This type of approach is typically developed by a partner or a supplier with the purpose of exchanging data from one application to another.

Cómo encontrar los plug-ins adecuados

Plugins can range quite dramatically in terms of quality. It’s important to realize and invest in the following:

• Understand the difference between plug1-to-1ins that realize a 1 to 1 integration and those that are linked to an iPaaS solution and are suitable for linking data to multiple applications. For instance, if the plugin is part of an ESB/iPaaS, you’ll receive all of the benefits of an ESB/iPaaS.
• Determine the certification of the plugins themselves. Have they been checked and certified by the relevant package? Is it well maintained? Is it a brand-new plugin without much experience?
• If you use a plugin, it’s important to remember that you can’t assume it’ll respond to custom wishes. In other words, customization is most likely impossible. In this case, it is important to plan and ensure that your customization needs are supported by the plugin that you’re choosing.

‍

Pros

Plugins can be brought to the market quickly, which means that they’re often quite cheap. You don’t have to send the same data to multiple applications if the plugin is already certified because it’ll automatically do the job. Plugins are great when you fall in the 80% category that suits that particular use case and when you don’t need customization now or in the future. And they also don’t have to be monitored, which means there’s no need to struggle with information integration.

‍

Contras

• It can become frustrating when you need customizations and can't determine exactly who is responsible for managing errors.
• No puedes enviar datos desde tu plugin a dos (o más) aplicaciones diferentes, por lo que no puedes reutilizar tus datos; tienes que construir una integración para cada conexión de software.
• La gestión de errores y el registro suelen ser mínimos y básicos, lo que te deja sin la posibilidad de recuperar datos sin reconstruir manualmente la integración.
• Los plugins pueden introducir otra herramienta que aprender con un grado variable de complejidad.
• Changing software in your IT landscape requires a big project and a big proc. Adding new functionalities can be near impossible. For mission-critical integrations, your team would be forced to create custom monitoring protocols, which are highly custom and expensive.
• Cuando las API se actualizan solas, pueden surgir problemas de comunicación.
• You'll need extra custom coding at some point to integrate new technologies like marketing automation software, AI, and machine learning tooling.

‍

El uso de plugins para integraciones es sólo una de las muchas formas de integrar sus aplicaciones. Obtenga más información descargando nuestro libro blanco gratuito "Cómo elegir una solución de integración".