Guest blog: How to select the right channel when integrating third-party services & applications
There’s a plethora of choice when it comes to selecting how you would like to access and integrate third-party applications to improve your business performance.
Cloud API or software-as-a-service (SaaS); on-premise or connector technology like Microsoft SQL Server? They all have their strengths, which include simplicity of integration, speed, security, automated maintenance and updates, for example.
Software-as-a-service (SaaS)
SaaS is one of the most popular options via which to integrate a third-party application. It is software hosted by a vendor in the cloud, accessible via a web connection and paid for as a subscription service. Because it’s simple, secure and fast to access over the internet, any service can be up and running on your systems usually within hours, rather than weeks or months.
With SaaS it’s easy to scale up and down as and when you need it. Updates and maintenance are handled by the provider, and it’s possible to access the application anywhere with a reliable internet connection.
Technical skills aren’t needed by the those using SaaS, as functions are usually designed to be straightforward and intuitive, enabling anyone in the organisation, with access rights, to be able to use and benefit from the services provided.
While security was once considered an issue, due to the fact it’s delivered by the cloud, it’s much less of a concern today, as security in the cloud has improved dramatically.
It’s for these reasons that SaaS is particularly suitable for startups, SMEs, organisations with scarce or no in-house technical skills for integration, or those without the budget to use third-party integrators.
Cloud APIs
One of the most common forms of service access today are via cloud APIs.
They are interface access points to software programmes that facilitate the transmission of data and services between cloud computing services, cloud services and devices, and on-premise applications.
With APIs it’s possible to share functionalities across multiple platforms and applications, without the requirement to rewrite code or rebuild existing functions into new apps.
Using cloud-based APIs it’s straightforward to inject data quality capabilities, for example, into any existing platform, such as master data management (MDM), regardless of what software or systems the organisation might already be using. Additionally, via cloud APIs the suitable service can be delivered quickly online.
Flexibility is a key advantage of using cloud APIs as an access method, because the service can be ‘injected’ anywhere in an organisation’s process flow, and can be modified to fit the individual use cases, as required.
Bear in mind that someone or a team with the relevant technical skills are needed to integrate a service using an API. However, this may not necessarily be overly complex, depending on the integration required, as vendors usually offer sample code to speed the process.
Plugin & connector technology – example: Microsoft SQL Server
Microsoft SQL Server – a database management system – is used by many in the public sector, particularly the NHS. It offers a great route to easily access services via SQL Server Integration Services (SSIS) which acts as a connecter between systems, and functions at a high operating speed. Tools can be simply accessed without further integration - it’s possible to just drag, drop and start using.
Other plugins for major platforms can be employed to help minimise the integration of services, such as for SalesForce & MS Dynamics, for instance.
While plugins help make integration more straightforward, this can be at the expense of flexibility due to the standardised out of the box set up many have.
On-premise
On-premise systems sit behind your organisation’s firewall, and retains all its processes, services, and data on local servers within your organisation, without the need of an internet connection or a web feed.
This technology is relevant for organisations who want ultimate control to protect their data. While it doesn’t mean they are any less likely to be hacked, it does mean that the ability to hack into their system is wholly dependant on their own controls.
On-premise also ensures that you have complete governance internally over areas such as: access, security, compliance, maintenance and improvements.
Throughput speed determination for processes can be an additional benefit of taking this approach, as the organisation itself can determine how the service is deployed internally on its servers and processors to reflect the urgency, frequency and scale of the processing.
It’s important to recognise with on-premise that the upkeep of all applications and systems can be very labour-intensive. Responsibility for uploading updates locally, maintenance, security, deployment, future-proofing, and anything else that the on-premise systems require to make them suitable for your business’ needs and changing requirements lies with you.
Therefore, your own IT and support teams need to be on hand to work on the system. Because of all these complexities, deployment can take longer than via cloud-based channels, and ongoing maintenance and support costs could be higher.
As a result of the additional self-determined security it delivers by being behind your own firewall on-premise stands out as a good system for heavily regulated industries like banking or government services.
Cloud-based options sometimes the only option
It is important to recognise that because of the nature of the service required, such as electronic ID verification (eIDV), that a cloud API or SaaS option are the only meaningful routes to take. The reason is to work effectively such a service requires huge amounts of up-to-date data which can only be effectively delivered, in real-time, over the internet.
eIDV
Being accessed via a cloud API or SaaS, eIDV is delivered as a scalable easy to deploy platform that supports cross-checks against an individual's contact data in real-time as they complete an online application process. It is able to do this by matching the name, address, date of birth, email or phone number against reputable data streams, such as government agency, credit agency and utility records, along with mortality screening checks, to effectively confirm the ID of an individual. Additionally, such technology should be able to highlight those who have been sanctioned, politically exposed persons (PEPs), offer adverse media screening and know your business (KYB) checks, for a full ID verification service that helps to prevent fraud.
In conclusion
The various channels that enable organisations to access third-party applications all have their strengths. It’s a case of sourcing a provider offering a service you require along with the delivery option that suits your needs. Furthermore, they must offer support and training on using the channel that works for you, as well as on their service.
This guest blog was written by Barley Laing, UK Managing Director at Melissa. To learn more about Melissa, please visit their LinkedIn and Twitter page.
Authors
Barley Laing
Barley Laing joined Melissa and set up the UK office in 2014 during an exciting expansion phase of the California headquartered company.