The first official Kloudless webinar has come and gone, and we’re so thankful to all of you that turned out to hear our take on the future of IT Enterprise API integrations. If you didn’t get a chance to make it to the live session, please click here to watch the webinar in its entirety. What follows is a breakdown of what was covered during the webinar, as well as some answers to the questions we received.
There are over 20,000 public APIs available today. They exist because businesses increasingly rely on highly specialized cloud apps for their productivity, causing the need for interoperability to increase.
However, the status quo puts the onus on customers to tie their apps together. App developers direct customers to a public API in the hope that they build the integration themselves; IPaaS vendors provide platforms for customers to build workflows. The result of these poor quality integrations – re-invented by each customer – is a poor user experience overall, and less engagement with SaaS apps.
Ideally, we would shift the burden to apps to work with each other out of the box. There is no universal data format for categorical cloud services and the burden that this places on developers are increased with every additional API service their app connects with.
Users demand choice. Applications can no longer offer a single cloud storage service, as potential end-users will forgo the app entirely if a user’s preferred service is not offered. As the number of integrations increase, product roadmaps experience delays and time to market grows larger.
Even when highly-capable development teams work through the integration of multiple categorical cloud services, they are left with the plague of future maintenance every time an API updates its version or changes its responses.
In this talk, we will explore, through a demonstration of Kloudless File Explorer, how Kloudless can be used as an abstraction layer between apps to give developers the ability to integrate with all dozens of cloud-based services without learning how to use each individual API.
We received some great questions during the webinar. Here are the three that were addressed during the webinar:
Question: When an API is updated, to what degree do my in-house developers need to update our code using Kloudless vs. not?
Answer: Not at all, because Kloudless is essentially a passthrough, offering a single connection to the Unified APIs that stays constant. Whenever an API updates its versions or changes its response, Kloudless takes care of all the maintenance, relieving your developers of that burden.
Question: What about the data that gets left out of the Unified Data model? For instance, parameters that are unique to each cloud storage service?
Answer: With each separate service, the JSON response will be modeled differently, potentially leaving out some of the response after being sent through the Unified data model. In cases where you need to retrieve some data that isn’t present in the unified data model, Kloudless allows for the raw response to be retrieved so you can bypass the unified data model if you need to retrieve additional data.
Question: Is the File Explorer included with the cloud storage integration or is it a separate feature?
Answer: The File Explorer is free and included in the Unified Cloud Storage API. It can be used on a free account with up to 100 connected user accounts. You can thoroughly test and configure it completely by connecting some applications and editing the stylesheets to fit your organization’s needs. All these features and functionality are also available through Kloudless’ authenticator library and routes, so your application’s API can implement any of its functionality without needing to use the File Explorer UI Tool
We look forward to seeing all of you at the next webinar in September. Until then, view the webinar in its entirety by clicking here.