Deepak Nadig discusses how PayPal’s API Platform evolved both internally and externally, the principles and patterns used, and how it is enabling the future of Money.
Cedric Champeau discusses the concept of traits introduced by Groovy 2.3. Traits look like interfaces, but allow the developer to add both implementation and state into it.
Michael Garvey discusses about understanding of common challenges, and learning strategies, principles and practices to overcome them and craft better design for your interfaces.
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.
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.
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.
Baruch Sadogursky discusses creating DSLs which support plugins written both in Groovy or Java, addressing good public API design practices, security, and classpath isolation.
Bobby Warner discusses the features available in Grails 2.3 to build RESTful APIs.
Graeme Rocher talks through the latest Async features offered by Grails and how they can be used to create non-blocking REST APIs.
Deepak Nadig, Praveen Alavilli present how PayPal redesigned its APIs based on lessons learnt developing their services in over 14 years, and the principles, patterns and anti-patterns used.