Stefan Krawczyk discusses how StitchFix used the cloud to enable over 80 data scientists to be productive and have easy access, covering prototyping, algorithms used, keeping schema in sync, etc.
Tom Faulhaber discusses the new container-based toolbox for building systems that are robust in the face of failures, how to recover from failure and how the tools can be used to best effect.
Martina Iglesias Fernández discusses Spotify’s approach to documentation through automatic discovery of existing endpoints, service configuration, and deployment information at runtime.
Rob Harrop discusses the increasing automated field of operations and what the future might hold when machine learning and AI techniques are brought to bear on the problem of systems operations.
Tod Golding discusses the architecture and design strategies associated with building and delivering SaaS solutions in a serverless model.
Glenn Block discusses the truth and myth beyond some beliefs: the web was built for hypermedia, there is no REST without hypermedia, hypermedia is the magic cure for all API ills, etc.
Joe Kutner talks about Kafka and where it fits in a Spring app and how to make it do things message queues simply can't.
Oleg Zhurakousky discusses the Hadoop ecosystem – Hadoop, HDFS, Yarn-, and how projects such as Hive, Atlas, NiFi interact and integrate to support the variety of data used for analytics.
Chun-Ho Hung and Nikhil Garg discuss Quanta, Quora's counting system powering their high-volume near-real-time analytics, describing the architecture, design goals, constraints, and choices made.
Andreas Evers introduces Spring REST Docs and its test-driven approach to RESTful API documentation.
David Julia describes some patterns that Pivotal Labs have employed over the last two years of building Spring Boot based microservices in the context of legacy systems.
The speakers discuss the organizational structure and communication and development strategies and tools to allow teams to work in parallel without drowning in process overhead and coordination costs.