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.
In this solutions track talk, sponsored by WSO2, Paul Fremantle explores open source approaches to APIs and PaaS to create new digital connected ecosystems. He takes a look at organizations that have done this: how, why, and what the results are.
In this solutions track talk, sponsored by Intel, Peter Logan looks at the evolution of the service layer in the context of the new prevailing developments in API management and describes new architectural approaches an enterprise can take as they look to merge these two worlds, taking the best practices from both domains.
Baruch Sadogursky discusses creating DSLs which support plugins written both in Groovy or Java, addressing good public API design practices, security, and classpath isolation.