Steven Ihde and Karan Parikh discuss about tools and frameworks built in order to help LinkedIn's transition to microservices, including their URN resolution engine and the Rest.li API Hub.
Paul Osman discusses their experiences evolving 500px from a single, monolithic Ruby on Rails application to a series of composable microservices written in Ruby and Go.
Martin Thompson focuses on the design of Aeron, what they learned trying to achieve consistent performance, and challenges performing UDP messaging in a lock-free and wait-free manner.
Caitie McCaffrey does an overview of Orleans, the challenges faced when building the Halo 4 services, and why the Actor Model and Orleans in particular were utilized to solve these problems.
Russ Olsen tells the moon landing story and how it has affected the software development.
Thore Thomassen shares from experience how to combine structured data in a DWH with unstructured data in NoSQL, and using parallel data warehouse appliances to boost the analytical capabilities.
Adam Parker tells how they planned and ran a diary study, what they did during the 3 weeks of the study, how they analyzed the results, and what they learned by doing it.
Kevlin Henney looks at how uncertainty, lack of knowledge and options can be used to partition and structure the code in a system.
Colin Burns takes a look at the creative forces shaping BBC’s approach to the future, examining how to create innovative experiences across different screens.
Chad Fowler attempts to convince people that keeping things "tiny" –small iterations, small methods, small teams - is the best thing one can do for himself and his team.
Thomas Kristensen describes the overall architecture of Composer, a system for composing musing, showing how to build a system that achieves responsiveness while still being flexible.
Gian Merlino presents the advantages, challenges, and best practices to deploying and maintaining lambda architectures in the real world, using the infrastructure at Metamarkets as a case study.