May 31, 2014
Single purpose API
Related Articles (828)
When a federal judge declared in June that software APIs aren’t covered by copyright law, it was a major victory not just for Google against Oracle, but for the API developers and users alike.
It's funny that when I talk to people in the travel industry about mashups and APIs, most of them get glazed looks in their eyes. Throw in terms like location based services or geospatial awareness and I've lost them. What most of them don't realize is that the majority of the travel apps that are starting to come out, both online and for mobile are mashups that are relying on location awareness and geospatial data. Many of them, like Pocketvillage are a consumer interface on top of a variety of APIs all normalized for a single homogenous user experience. That's right, it's essentially a metasearch tool that pulls in content from a variety of sources including Viator, GetYourGuide, TourCMS, Rezgo, AirBnB, and many others. What differentiates a metasearch like Pocketvillage from other metasearch applications however, is the fact that with location based services enabled, Pocketvillage can return content based on your current location. The issue right now however is that not all geo data is equal. Not all APIs provide geolocation information and some return it based on different criteria.
Google Cloud Platform continues to roll out consistent updates to its App Engine platform-as-a-service (PaaS). Its latest release, version 1.9.0, makes available App Engine Modules, which aims to help developers break their applications into logical components to bring significant efficiency to both cost and performance. The update also includes a MapReduce library for Java and several PHP Runtime improvements.