Ken Kousen discusses combining various technologies: Groovy, Ratpack, MongoDB, Grails, REST.
Dave Farley discusses the problems raised by inefficient processes creating poor quality output, too late to capitalise on the expected business value, and proposes solutions to them.
Richard Rodger discusses measuring the benefits of using microservices from a business perspective in order to evaluate their impact on an organization.
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.
Robert Reppel considers that architects should build software-centric systems as a user experience for customers, products owners, developers, IT, testers and other participants.
James Lewis describes a common trait seen in organizations using microservices: decentralized governance based on polyglot programming and decentralized product teams.
Shobana Radhakrishnan shares details about best practices adopted in implementing API integration with third party services, how to manage change and deal with failures.
Ken Kousen demonstrates the RESTful features in Grails and shows how to take advantage of them with annotations, controllers, renderers and more.
Stephen Grafton shares from his experience working with distributed teams in a large organization, bringing together business and agile practices.
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.