Summly: An Award Winning Mobile App's Journey to the Cloud with Five-9s Availability on a Shoestring Budget
Eugene Ciurana describes the architectural choices, servers configuration, database, and caching systems that enabled Summly to achieve Five-9-Availability with deployments across transcontinental availability zones.
Hosted by Erik Meijer, who runs the Cloud Programmability Team at Microsoft, the panelists answer questions on C/C++ and Java performance, contrasting the virtues of native vs. managed code.
Crista Lopes discusses if scale affects the internal structure of projects and whether the popularity of libraries is correlated with internal software metrics such as bug density based on analyzing the source code of 30,000 open source Java projects.
Jordan DeLong overviews the past, current and near future "good parts" of C++'s functional side through the colored lens of his biases.
Delivering Performance Under Schedule and Resource Pressure: Lessons Learned at Google and Microsoft
Ivan Filho shares lessons learned during the development and release of several large scale services at Microsoft and Google from the perspective of a performance manager.
David Leibs unveils some of features of Mathematica Programming Language, a functional and dynamically typed programming language.
Raffi Krikorian discusses the software engineering challenges met re-architecting Twitter and the cultural change impact that came with it.
Christian Legnitto offers insight in some of the tools and processes used by Facebook for pushing new updates to their mobile apps.
Ashley Johnson identifies key principles for high performance product development teams, and explore which of these we can and cannot control in virtual teams.
Gil Tene examines the core issues that have historically kept Java environments from performing well in low latency environments and how it can perform now without trade-offs and compromises.
Tom Santero explores the various configurations of distributed teams, dissecting both productive as well as undesirable qualities that emerge when working remotely. We will postulate that distributed teams are novel and worth considering, but ultimately impossible to reduce and replicate.