James Coplien explains the DCI paradigm used to better represent the user’s mental model through code, proposing a way of reintroducing architecture back to Lean and Agile projects.
Lars George and Fabrizio Schmidt present Germany’s largest social networks, Schuelervz, Studivz and Meinvz, the initial architecture, why it didn’t work and how they solved it with a NoSQL solution.
Simon Oxley presents how his team built a monitoring and reporting web app, the challenges encountered and decisions made, the technologies and tools used, and what are the their plans for the future.
Simon Stewart presents how Google’s Engineering Productivity team and Software Engineers in Test (SETs) help developers to make their code more maintainable, recommending some of their tools.
Justin Sheehy explains the principles behind concurrent distributed systems: no global state, no ACID but rather BASE, no RPC but protocols over APIs, prepare for failure, degradation, measurement.
Jon Skeet presents Noda Time, a .NET port of Joda Time which is a Java library for handling time. Skeet discusses the troubles handling time with the .NET API, and how Noda Time solves those issues.
Torrey Rice presents relevant milestones in the evolution of the web from a UX perspective and tries to foresee the future of web development and what it will mean for developers and casual people.
Geir Magnusson explains why Gilt Groupe is using Project Voldemort to scale out their e-commerce transactional system, what are the benefits and what is the current architecture after ditching SQL.
Julian Simpson thinks dev and ops should be one team, achieved through: collaboration, respecting everyone, having lunch together, co-location, discussing problems, joined retrospectives, etc.
Alex Buckley presents some of the challenges for JVM to become a universal VM, serving the needs of Java and non-Java languages, static and dynamic languages, and an ever growing number of features.
Oren Eini presents several architectural concepts – divide and conquer, background evaluation, one way messaging, the single responsibility principle - helpful to build highly scalable systems.