Rebecca Parsons, Thoughtworks CTO, on microservices: prerequisites, challenges and benefits. Also insights on designing services for scalability, handling failure and eventual consistency.
Mike Long explains how to build software for the long term, software maintenance, how some software survives. Also a thought experiment - how would you build software that lasts for 10,000 years?
Yan Cui talks about the advantages of using F# to build DSLs and using the actor model. Also: why and how to use graph databases to model (game) economies.
Natalia Chechina explains the challenges of scaling distributed Erlang beyond a certain number of systems and how SD Erlang helps to overcome those problems.
Barbara Fusinska explains the challenges of building offline mobile applications: synchronisation, API design, data modeling, and much more.
Turing Award winner Leslie Lamport talks to Charles Humble about LaTeX, Paxos, his "Time, Clocks and the Ordering of Events in a Distributed System" paper, TLA and TLA+
Peter Bourgon discusses distributed programming with commutative replicated data types (CRDTs), how they work, what problems they solve, and his experience with using the Go language at SoundCloud.
Al Tsang talks about using Node.js to build Web APIs, the emergence of an API economy, the convergence between an API Gateway and an ESB, and Node Forward Group's decision to fork Node.
Jeff Lindsay explains the difference between virtualization and containers, what Docker brings to the table, best practices for using containers and what to avoid, and much more.
Chris discusses the rise of CQRS and Event Sourcing as a solution for all domains. With the advent of Docker, applications that manage complex domains can be built tested and deployed in minutes. Chris talks about the reasons for choosing a CQRS and Event Sourced solution as well as how the addition of Docker can help an organization embrace Continuous Delivery by using existing tools.
Jerome Louvel talks about Web APIs, the Restlet framework and his latest venture APISpark
Yoni Goldberg explains Gilt's architecture which consists of 350+ microservices, how teams decide the scope of a microservice, API design and management, monitoring, Scala at Gilt and much more.