A customer of ours once said it best - “...most open APIs start out as little more than raw, naked, features exposed to developers, and there is a big gap between a feature and a full-fledged service.” This e-book is about the capabilities ‘around the API’ that might be needed to ‘productize’, ‘monetize’, or ‘operationalize’ an API-based service.

As the API and apps economy continues to evolve, a design problem arises for API designers when internal systems are too complex to expose directly to app developers. The goal of an API Facade Pattern is to articulate those internal systems and make them useful and consumable by app developers.

In April 2012, O'Reilly hosted a webinar by the authors of the O'Reilly book "APIs: A Strategy Guide." Video and slides are below. The book is an overview of API strategy for business executives and this webinar dives into both public and private API strategies. Thanks to O'Reilly, @daniel_jacobson, @gbrail and @danwoodscito. Courtesy of O'Reilly, a free chapter is posted here.

API Design Tour - Digital River (Webcast)

What makes for a great API design? What will make the developers who use your API successful quickly? What debates and decisions go on behind the scenes before an API team launches an API?

OData Introduction and Impact on API Design (Webcast)

We're in a data-driven and Web API economy. Web API designers need to define what and how data should be exposed from a variety of apps, services, and stores. What are the challenges of unlocking your data and opening up access in a straightforward and standards-compliant manner? Is OData the right tool for the job? What does it mean from the point of view of designing an API?

HATEOAS 101: Opinionated Introduction to a REST API Style - Webcast

An introduction to HATEOAS core principles, examples, and a look at the value of the approach for API providers and app developers.

The API Facade Pattern: People - Episode 4

The fourth and final episode in the API Facade Pattern series: covers people considerations—the team structures, the roles and responsibilities and the politics—for building and using an API facade.

Pages