November 16, 2016
View all 2 Followers
View all 830 Related Articles
Related Articles (830)
One of the big debates these days when it comes to cloud computing center around portability and interoperatbilty between providers. That is, if you build an application on Amazon's EC2 or Google's AppEngine or Force.com, or store your data on Box.net or Amazon's S3, how hard is it to port your application or move your data to another cloud provider? If you develop on a given platform, how locked-in, or not, are you? And beyond that, could developers benefit from having standardized APIs to develop to without having to learn a new model and interface each time. As you'd expect, there's no easy answer to this.
Plivo was founded after its founders, Venky Balasubramanian and Michael Ricordeau, found each other on Github and collectively decided, "[t]elephony is complex." Today, Plivo's focus is simple in statement, but complex in execution: Plivo offers "simple and powerful APIs that make it easier for businesses to develop telephony applications." Plivo's building block APIs allow developers to create telephony applications without learning the nuts and bolts of legacy telephony.
Step back almost 20 years. I was then CEO of a tiny publishing house at a group breakfast during what was then called the American Booksellers Association convention. The guest speaker was a guy with a clearly nutty idea: Jeff Bezos was selling books over the Internet. Every publisher in the room had the same question: who in their right mind would ever buy a book that you couldn't hold in your hands before paying for it?