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.
Ryan Gardner focuses on how Dealer.com leveraged the powerful attributes of both Apache ZooKeeper and Spring to rid their application of local configuration files.
Colin Garlick presents a foundation of value for the practice of architecture, starting with the values that architecture is established on, showing what's important for an architecture.
Adam Tornhill teaches how to predict bugs, detect architectural decay and find the code that is most expensive to maintain, how to evaluate knowledge drain in a codebase, and much more.
Roy Rapoport shares some of the lessons Netflix learned building a monitoring system, the challenges, pitfalls and opportunities encountered along the way.
Rebecca Parsons explores the relationship between evolutionary architecture, continuous delivery and microservices, focusing on how they support each other in the creation of complex systems.
Paul Butcher advises on using concurrency the right way in order to avoid its pitfalls.
Jack Schulze discusses the emerging design domain of connected products and the challenge of representing systems through interfaces in the emerging world of connected devices.
Phillip Trelford explains how compilers work with live code samples, primarily in F# and C#, covering language design and parsing, all-the-way through to emitting code.
Ben Hall takes a dive at where to begin along with the mind-set and tooling required to quickly and effectively create prototypes.
Francesco Cesarini illustrates how the Erlang way of thinking about problems leads to scalable and fault-tolerant designs, describing 3 ways of clustering Erlang nodes within the server side domain.