At Backupify we know cloud backup since we’ve been at it for years and it’s all we do. Cloud application backup is different than traditional backup. We define “traditional backup” as anything that gets your backup from files. We’re different because the source of your backup data is some set of APIs; that source is not a consistent, reusable standard like a file descriptor. Because of this particular characteristic, we’re making critical, technical investments every day in the APIs of the various cloud apps we’re backing up.
APIs are quite different compared to file descriptors because:
Every data source is different - Each time we add a new cloud application to back up we need to learn a new API, and no two APIs are the same.
APIs change over time - APIs are living, evolving pieces of software, changing far more often than file descriptor interfaces. We constantly update our software to keep up with new versions and deprecated calls.
APIs often limit access / bandwidth - Backups move a tremendous amount of data. Our code must be prepared to self-rate-limit, or pause/resume based on whatever “good API citizens” need to do for the particular API being worked with: including bandwidth, simultaneous connections or call-limits.
APIs are less stable than hardware-based interfaces to files - We are always prepared to work around bugs in the underlying APIs to collect the data our customers require.
This week we announced that the Backupify Developer Platform is live. The platform is a set of APIs designed to reduce the cost (and energy) associated with cloud-to-cloud backup. This platform is the result of LOTS of hard work on our part so we’re thrilled to see it in action.
We’ve got a powerful platform that helps make cloud-to-cloud backup seamless. With what we call descriptive-endpoint technology, we’ve provided a meta-language through our APIs to data-driven cloud application backup. Using this technology, cloud application API endpoints are easily described: including URLs, key parameter mappings, and meta-data mappings in the response. With that description in hand, our platform does the rest: provisioning, authentication, data collection, encryption, storage, and data-access are simply “taken care of.”
We are already using this technology within Backupify to speed up the creation of backup offerings for additional cloud applications. This means that we can reduce the amount of time it takes us to create a scalable, new backup solution from weeks to days (or even hours in some cases). But that isn’t the coolest part.
The coolest part is that the API is available to any cloud application developer to use.
We have already seen a huge groundswell of interest in using this: especially from cloud application providers themselves. We’re in the process of launching our first external partner using these APIs, and we have additional partners ready to go. We’ll be naming names and talking about each of these companies in more detail as they go live. So stay tuned!