John Slaby discusses the reasons why he prefers fluent APIs and examine, through examples, the many different ways that Fluent APIs can be used to help produce better solutions than external DSLs.
Simon Redfern presents how the Open Bank Project innovates by leveraging open APIs, open source and open data, making banking data more accessible via an ecosystem of apps and services.
David Galeano discusses what type of games are possible in the browser today, and what language features and APIs are needed to create the next generation of games.
Paul Hill presents a case study of building an API with a short deadline using Node.js, WebSocket, MongoDB, JSON, Promises, Swagger, Memcached, Varnish and Hypermedia ReST.
Adrian Cockcroft discusses strategies, patterns and pathways to perform a gradual migration from monolithic applications towards cloud-based REST microservices.
John Musser takes a look at some of the common mistakes made by API providers, providing advice on what can be done to avoid them.
Tomas Petricek introduces F#’s capabilities in dealing with scientific data: type providers -CSV, XML, JSON, REST-, interactive development, data visualization libraries, integration with R or MathLab
Ted Epstein shows how a shared canonical model can make life easier for API consumers, while still allowing the flexibility to expose different services, with different contextual requirements.
Todd Montgomery explains using WebSocket and reactive programming in an event driven RESTful architecture for the emerging IoT world.
Brandon Byars discusses the constraints and the flexibility of nonpublic APIs, and lessons learned from scaling RESTful integration across more than a dozen teams.
Jon Skeet provides practical advice on designing APIs using immutability, separation of concerns and other principles, resulting in elegant and reusable code.