As more and more Web and mobile applications utilize APIs to drive their respective front ends, performance becomes an emerging concern. XML, long used as a method for exchanging data, is giving way to JSON, now considered the gold standard. But is JSON always the right choice over XML? This article examines the foundations of JSON and XML and the differences between them, providing recommendations for how to choose the right path.
Writing API documentation for software being created with an agile process can be especially challenging because what is being documented is constantly being changed. Project managers and developer leads must assign resources to writers up front, and writers should speak up as soon as issues arise because documentation challenges can snowball much faster in an agile environment.
A workshop on open government data pathways by API Evangelist and current White House Innovation Fellow, Kin Lane, shows there is still plenty of potential for developers, startups and interested citizens to influence the government open data agenda and make use of government data assets. Lane ran the workshop as part of the pre-opening day’s workshop series at API Strategy and Practice, being held in San Francisco for the rest of the week.
Any company that makes an API knows that just having the API is not enough. A bare endpoint is probably worse than not having an API at all. To make your API and platform useful you need documentation, tools, examples and forums. If you are a successful API company you start developing a community of people that work with your service. The community shares ideas and helps each other out.
Last month ProgrammableWeb reported that Codecademy had launched a new curriculum featuring website and application development using APIs. Codecademy has just announced the addition of new APIs and courses to the curriculum.
I really like playing around with cutting edge technologies. One of them is GoodData CloudConnect, the tool for ETL and building GoodData projects. Since we released this new feature, I have dozens of ideas how the data from various sources can be easily transformed in the cloud. Recently, for example, I found myself wondering: “How about using the Google BigQuery API as a data source? What about visualizing the data from it in GoodData?”
Hystrix: it’s the genus name for “Old World” porcupines, and it’s also the latest release from Netflix. But you won’t see it in their catalog of movie and TV titles, and you can’t add it to your queue, because it’s not content–it’s how Netflix makes sure its content is highly available. Now, Netflix has made Hystrix open source, for anyone using Amazon Web Services (AWS) to implement in their own cloud applications. Read on for details on this “resilience engineering” code library.
There’s a lot that’s been written about the content of API documentation, but what about its look-and-feel? Unlike many types of information, API documentation is not meant to be read front-to-back, but is meant to be scanned for relevant information. This means that the look-and-feel should be very clean. Clarity is a much higher priority than aesthetics.
Google BigQuery is a REST-based API for SQL-like analysis of billions of rows of data in just a few seconds. Customers are using it to analyze advertising campaigns, web server logs, inventory availability and more. While BigQuery makes it easy for customers to gain insights into massive datasets, it can be challenging to make sense of the results without the power of visualization. The Google BigQuery browser tool doesn’t have visualization built in, but the API enables you to integrate with other tools in just a few dozen lines of code.
Pearson is a worldwide educational publishing company that provides learning materials, certifications, and multimedia learning tools. The company has access to an amazing amount of data surrounding a seemingly endless list of topics. Now, with the Pearson Kitchen Manager API developers can tap into at least a portion of Pearson’s knowledge base.