While there’s a lot of chest-thumping going on over who has the biggest cloud, there’s no doubt that IBM suddenly has a lot of momentum following its acquisition of SoftLayer. Amazon Web Services (AWS) remains the largest public cloud service by far in terms of the pure number of virtual machines. But when you consider more than just infrastructure-as-a-service (IaaS) in the cloud, IBM claims to have generated $4.4 billion in revenue across a cloud ecosystem that includes SoftLayer, 150 software-as-a-service (SaaS) applications and a vast array of cloud consulting services.
At the end of last month, W3C published a draft NFC API. As a leading authority on developing Web standards, I found it interesting that W3C had dedicated time and resources to NFC technology. NFC certainly received significant hype when it first showed up in consumer devices; however, since its initial 15 minutes of fame, many have questioned the viability, need, and long-term possibilities of NFC as a mainstream technology. Accordingly, I reached out to the W3C Team Contact for the NFC Working Group, Dave Raggett.
There are trillions of dollars in transactions that to this day still depend on mainframes to be processed. This means any API economy that wants to succeed must ultimately include one of the most venerable platforms in all of enterprise IT.
Given the rabid nature of most of their fan base, professional football teams were among the first organizations to see the value of developing mobile applications to get closer to those fans. The problem for most teams now is the stadium WiFi experience they provide to their most loyal fans leaves much to be desired.
The benefits of a well-designed, well-implemented, easily integated API are well known: happier developers, higher usage and, hopefully, greater profit as a result. While many high-level best practices for developing a great API have been established, a failure to pay close attention to small details, such as parameter defaults, can create big headaches.
The tension that has been building for months between Amazon and supporters of the OpenStack cloud computing framework is finally starting to boil over. This week Hewlett-Packard announced that it will no longer support the Amazon Web Services API on the public cloud computing service it unfurled earlier this week. According to a statement released to ProgrammableWeb by by Roger Levy, vice president and general manager for HP Public Cloud, the issue comes down to Amazon’s ongoing effort to lock customers into a proprietary API.
With both delivery and management of security increasingly moving to the cloud, organizations of all sizes are presented with new approaches to security that use APIs to reduce the complexity of securing applications.
As part of a presentation at APIDays today, Jerome Louvel, CEO of APISpark announced the all-in-one API web management platform has now moved into an open beta stage. As a result, developers can sign up and gain access to the platform immediately, without awaiting a registration approval stage.
It may take some getting used to, but with more control over applications, developers will have to assume a lot more responsibility for their performance. At the Node Summit yesterday, F5 Networks announced that it is leveraging technology gained via its acquisition of LineRate Systems to allow developers to customize Web traffic via an API created using the Node.js framework.
Google Compute Engine is now Generally Available to Developers. GCE offers Linux Virtual Machines, where you can host your applications, powered by Google’s infrastructure. The service was first announced at I/O 2012 and has seen consistent announcements in terms of features, performance benchmarks, security and a host of network infrastructure capabilities over the year.