Ross Zhang and Jun Li talk about how they have successfully solved many puzzle pieces with migrating traditional Java enterprise applications using Spring Boot, Spring Cloud and Cloud Foundry.
Alois Reitbauer discusses challenges and solutions on the organizational, development and operational side, deploying faster, decoupling a monolith without breaking the logic and dynamically scaling.
Nick Beenham describes how the Enterprise Services Team at Comcast transformed from large monolithic deployments with cycle times of anything from 90 days to cycle times measured in hours.
Peter Lawrey discusses the differences between microservices and monolith architectures, their relative benefits and disadvantages, patterns and strategies implementing low latency microservices.
Amit Gupta talks about how Cloud Foundry does continuous integration, from a GitHub pull request against a small repository to an official final release, transparently working with the community.
Leonard Garvey and Louis Simoneau discuss how to decompose a monolith, architectural and integration patterns to avoid creating a monolith, and useful patterns and tools along the way.
Erik Costlow discusses what to consider when upgrading to Java 9, where to find early access releases and how to analyze library dependencies for unintentional reliance internal APIs.
Tim Pettersen covers Git LFS internals & architecture, CLI usage, team workflows and how to use it with Eclipse EGit, providing practical advice for those interested in using Git LFS.
Matthias Sohn presents the Git features that are implemented in Eclipse Neon including git-flow commands, support for attributes, hooks and filters, versioning large binary files and others.
Dustin Hudson discusses enterprise architecture using case studies and life examples to illustrate how to put together legacy systems and third-party apps while considering user-driven decisions.
Anil Madhavapeddy introduces the Irmin library by means of a functional queue, shows how the Git mirroring works, and then demonstrates some more complex applications.
Kevlin Henney examines some examples of code that are interesting because of historical significance, profound concepts, impressive technique, exemplary style or just sheer geekiness.