iPaaS

As with any selection of technology, buyers should take the time to validate the features that are important to them. Time invested in proving exercises to validate capability is time saved in deployment or redeployment of another technology further down the track. All integration technologies can generally be made to work for nearly all integration scenarios. Again, this is where valuing the solution and the data are important factors to consider. We can bend technology to fit almost any scenario. The questions should be: does the value stack up at the end? and Did we lean on the technology the right way?

Whilst many IPaaS vendors can tell a big data story it isn’t generally something we associate with it. There’s a tipping point on volume where we might consider event streaming as a more appropriate technology. Organisations with strict regulatory requirements around data processing and residency may have issues/challenges with IPaaS under some circumstances. Likewise with respect to organisations for whom API monetisation is a key part of their business. They may find API Management capability a little too rudimentary in some IPaaS platforms. 

Low-code and easy deployment technologies bring compromises in order to deliver on the features they support. Coding visually tends to lock us into the platform we are using as does simplified deployment. The complexity in using a standards based ESB also affords a fair degree of portability across vendor technologies. It’s important for buyers to understand the compromises and whether or not the benefits associated with those are something the organisation can live with.