Cloud APIs are all about the endpoints: some services follow the current trend of providing a RESTful end point, others use older protocols such as RPC or SOAP, some use newer - push focused - endpoints like WebSockets or HTTP Streaming, others may offer a number of different endpoints to meet different requirements and some just use what seems to be best for a specific job which might mean not strictly following protocol rules. But is providing an endpoint to a service alone good enough? Should a developer really have to care about how a service is built or accessed when they can use a client library?
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.
The trouble with building mobile computing applications is that end users have little tolerance when it comes to how they expect those applications to behave. Never mind the fact that mobile applications are amongst some of the most challenging to create; the second somebody has a less than optimal experience they're off to another application. Needless to say, that puts a lot of pressure on mobile application developers.