Fork me on GitHub

I reviewed the deployment the FBOpen API the other day, which is a simple API resource of business opportunities with the U.S. Federal Government. An interesting aspect of the FBOpen implementation was that 18F used Solr to deploy the API layer.

Solr is an open source search tool developed by the Apache Software Foundation, which can take any document store and easily generate a simple, yet pretty powerful web API—opening up access to content, without costly infrastructure. I showcased how the Free Law Project launched the Court Opinion API, using Solr, opening up access to archives of legal documents from across the country.

18F took XML dumps of business opportunities from FBO.gov, then deployed Apache Solr as the API layer. You can download or fork 18F’s FBOpen API, and deploy the API in your own infrastructure. This provides a pretty interesting blueprint for how government can easily open up data, then launch an API for developers to build on top of.

I’m thinking that government data dumps, plus web API deployed using Solr, plus interactive documentation deployed via Github, combined with frictionless API access via api.data.gov or 3Scale, open licensing and terms of use—all sounds like a pretty health formula for open, reusable government API infrastructure.

Along with other healthy patterns for API design, deployment, management and evangelism I find out in the API space, I think what 18F has done with the FBOpen API, needs highlighting. I think government data plus web API using Solr is a recipe I’d like to see used across all government projects.




comments powered by Disqus
Google+