O'Reilly Software Architecture Conference 2016 - London, United Kingdom
2016-10-19..2016-10-21
London, United Kingdom
[O'Reilly Software Architecture Conference 2015, O'Reilly Software Architecture Conference 2016 - London, United Kingdom, O'Reilly Software Architecture Conference 2016: San Francisco, O'Reilly Software Architecture Conference 2017 - New York, New York, O'Reilly Software Architecture Conference 2019 - New York, New York]
who it's for
software architects, engineering managers, platform engineers, backend developers, devops engineers, technical leads
topics
reactive architecture with Akka and Erlang; immutable domain models; cluster sharding for scale; microservices migration (strangler pattern); circuit breaker and failover patterns; OpenShift lifecycle and scaling; streaming analytics with Spark; executable specifications (unit tests, RSpec, Cucumber); pair programming and team coaching; deployment frequency and failure rate metrics; polyglot data stores; predictive analytics for node resilience
| title | author | length |
|---|---|---|
| why software development is an engineering discipline | Glenn Vanderburg | 42m |
Argues software development is a legitimate engineering discipline, not a failed “software engineering” nor merely an art, by comparing practices and… | ||
| Reactive architecture, design, and programming | Duncan K. DeVore | 12m |
Defines reactive programming as models where A updates automatically when B and C change, then elevates that to reactive architecture which provides… | ||
| Moving from monolithic to microservices | Jorge Morales | 10m |
Enterprises move a monolith to microservices either by a risky big rewrite or strangler style incremental extraction, typically pulling components out first in… | ||
| Listening to the design pressures | Martin Thompson | 03m |
The label non-functional requirements is misleading because these concerns actually program behavior and determine architecture; think of them instead as… | ||
| The evolution of software architecture | Mark Richards | 02m |
Argues that three concrete forces drive architectural change and that modern styles arise when they combine: agility meaning speed plus coordination to react… | ||
| Microservices: Pros and cons | Rachel Laycock, Cassandra Shum | 03m |
Argument lays out concrete claims and concrete headaches: pro side argues for decentralized governance and choosing the right tool for the right job including… | ||
| The architecture of uncertainty | Kevlin Henney | 02m |
Argues that the common response to uncertainty — piling on abstractions and flexibility — usually makes systems worse and more complex rather than… | ||
| High-performance teams | Patrick Kua | 02m |
Argues architects need as much soft skill work as technical decisions and that the highest-leverage change is shaping how teams work rather than choosing… | ||
| Am I only streaming? Thinking reactive | Rob Harrop | 03m |
Claims that reactive is a practical evolution of 1978 CSP and 1973 actor ideas, reframing systems as data flows and transformations and showing reactive… | ||
| nothing matches | ||