Saul Caganoff looks at what service-oriented enterprises can learn from APIs and microservices to overcome both technical and cultural challenges.
Mike Amundsen describes a methodology for designing Web APIs (based on the book "RESTful Web APIs") that allows to map key aspects of a business into a usable, scalable, and flexible interface.
Niklas Gustavsson presents Spotify's 2-layer services, and how the UNIX philosophy of composing components that does a single thing well works on a greater scale.
Michael Bryzek presents lessons learned building an expansive microservice architecture at Gilt - an organization with 1500 git repositories and over 400 individual applications.
Torben Hoffmann talks about how to design systems with asynchronous message passing between processes that do not share any memory.
Todd Montgomery explores questions related to WebSocket, HTTP/2, CoAP, MQTT, XMPP, and the way these protocols change how services communicate.
Ken Kousen discusses combining various technologies: Groovy, Ratpack, MongoDB, Grails, REST.
Caoilte O'Connor explains how and when the Domain Service Aggregator Archetype can help, using the architectural evolution of "Video on Demand" in a broadcast company as a working example.
Glenn Renfro discusses how to create an application with a scheduler that will retrieve data from a web service, cleanse and emit the data via MQTT, by utilizing Spring Boot and Spring Integration.
Ken Kousen demonstrates the RESTful features in Grails and shows how to take advantage of them with annotations, controllers, renderers and more.
Steven Ihde and Karan Parikh discuss about tools and frameworks built in order to help LinkedIn's transition to microservices, including their URN resolution engine and the Rest.li API Hub.
Paul Osman discusses their experiences evolving 500px from a single, monolithic Ruby on Rails application to a series of composable microservices written in Ruby and Go.