Let's face it, if you want to take advantage of your application programming interface, API monetization is half the battle. Today we interview Bruno Pedro on his recommendations for different API business models that take advantage of great developer experience.Read More
The Hypermedia API is certainly a controversial topic, regaining traction as it is claimed to be a solution to the Internet of Things. This more accepted nickname for HATEOAS [Hypermedia as the Engine of Application State], has been around for awhile now, mainly in the HTTP space, but is making headlines again with new potential use cases. To jumpstart The API Economist again, we thought we’d start closer to home with one of our own Azure API Management team members Darrel Miller, co-host of YouTube channel “In the Mood for HTTP” and owner of the Bizcoder blog. Darrel is a veteran software developer with more than 20 years of experience in all things HTTP, Hypermedia, HttpClient and the Web API.Read More
API Economist: Is the reason why intellectual property and software are so challenging due to the sheer lack of case law that's been established?
Mark Radcliffe: I think that's part of it. But I also think you need to go back a little bit and talk about how software came to be covered by copyright. If you go back to the 1980s, there were very respectable intellectual property lawyers who would tell you that software was not copyrightable because it was a functional “work”. Only certain types of software would be copyrightable. Moreover, when the Copyright Act of 1976 was enacted, Congress deferred the decision about protecting software under copyright until they received a report from a special committee, the National Commission on New Technological Uses of Copyrighted Works (CONTU). Although CONTU recommended protection for software under copyright, one commissioner suggested that copyright not apply to “computer program in the form in which it is capable of being used to control computer operations.” Now the courts have made it very clear that software is protected by copyright, in fact almost any form of software is copyrightable. But copyright is actually a pretty poor fit for software. It's a poor fit because there's a large degree of functionality in software. Copyright was designed for music and literature and novels, things where you'd have immense scope in the choice of how you create the “work”.Read More
API Economist: There are a lot of different cloud offerings out there. Why do we need yet another abstraction layer for automating business processes?
Steve Wood: That's an interesting question. With ManyWho, we're doing more than just automating business processes. We're thinking about business processes as applications. For example, Salesforce represents a series of business processes in sales and in service and Exact Target in marketing. Both represent business processes embedded within those applications. Ultimately, much of the reason people use applications or build software is to automate or improve a process inside their business.Read More
API Economist: Cloud adoption is clearly accelerating in the enterprise. What are some of the biggest challenges that you're seeing with the typical enterprise wanting to move to the cloud?
Jared Wray: We see really two major problems that come up in the enterprise. One problem is, how are they are going to be able to move their resources and actually take advantage of the elasticity of cloud or even the services that come along with cloud? The second problem is, how do they architect legacy applications or even mold them into a better, fully distributed type of system? Those two problems are common in enterprise, and really there haven’t been great solutions to this day.Read More