Philip Wills believes that thinking about independent services and single responsibility applications rather than microservices can help to clarify the architectural complexity trade-offs.
Dan North and Jessica Kerr make a journey through complexity. At the other side we may find simplicity, or we may find the light at the end of the tunnel is just another oncoming ESB.
Greg Brougham introduces the Cynefin model and related practices which can be used to address uncertainty in the modern world.
Jon Hoffman discusses the general architecture, storage systems and development practices created to handle the ever increasing volume and complexity at Foursquare.
Jutta Eckstein provides insights in the latest scientific research on planning and shows how Beyond Budgeting and Agile principles can be combined so that even complex projects remain controllable.
Brian Degenhardt discusses lessons that Twitter learned managing a high rate of change and complexity, and how those can be applied anywhere.
Wojciech Seliga shares from experience how complex it can be to deal with thousands of tests -unit, functional, integration, performance- for Atlassian JIRA and what they did to bring it under control
Ian Robinson discusses the complexity of highly connected data and how graph databases can help, illustrating the talk with practical examples implemented using Neo4j.
Nathan Marz outlines several sources of complexity introduced in data systems - Lack of human fault-tolerance, Conﬂation of data and queries, Schemas done wrong - and what can be done to avoid them.
Stefan Tilkov suggests breaking a system into several subsystems, separating the micro and macro architecture, and addressing various integration issues in order to get a suppler architecture.
Michael Nygard outlines 8 rules for dealing with complex systems: Embrace Plurality, Contextualize Downstream, Beware Grandiosity, Decentralize, Isolate Failure Domains, Data Outlives Applications ...