David Rogers outlines how a highly-scalable RDF and SPARQL-based API was delivered, how a graph of highly-connected data can be managed effectively across a large organization, and their plans to open up access to the BBC's data from Bitesize learning resources, to the Radio 4 archive.
Paul Downey and David Heath discuss the UK Government Digital Service API Design Principles, the lessons learnt from building the GOV.UK publishing platform and transactional services on APIs, and how these design principles are now being applied to enable departments and agencies across government to transform transactions and services into becoming "digital by default".
Sanjiva Weerawarana keynotes on building a ecosystem and transforming the business into a service by creating and providing an API.
John Musser presents 20 API business models explaining how developers can make money with their APIs.
Ben Christensen describes how Neflix has optimized their API using a functional reactive programming (modeled after Rx) in a polyglot Java stack.
Daniel Jacobson shares advice on dealing with evolving APIs based on his experience with Netflix APIs.
Steve Klabnik discusses the importance of having an open API, believing that those who have it will succeed in the long run, and the others will fail.
Jeff Meisel shares insight in National Instruments’ attempt to create an open API for their software spanning 25 years.
OpenStack Extensions: Challenges and Lessons Learned in the Development and Governance of Extensible REST Services
Jorge Williams shares some of the challenges and lessons learned while adding extensions to OpenStack.
Mark Little provides advice on when it is not recommended to use transactions and how to use transactions with Web Services, NoSQL, REST and mobile infrastructures.
Jon Brisbin explains how to expose JPA entities via the Spring Data Repository abstraction and then exporting them to HTTP using Spring Data REST.