Phil Calcado shares the toolkit and strategy SoundCloud uses to keep its microservices explosion manageable, dealing with operations overhead, DevOps, breaking changes and asynchronous behaviors.
Paul Glavich discusses design decisions to be made when building a new API regarding versioning, hypermedia usage, authentication and other aspects.
Stuart Williams shares from experience how his company implemented Kanban, what worked for them in handling maintenance, support and a number of small projects.
Aaron Quint shares an honest story of a team's journey, taken from his experience as CTO of Paperless Post, an organization which went from 5 to over 100 people and from a dev team of 2 to 40.
Guy Davidson, Tom Miles discuss 64-bit programming pitfalls, Unity builds, writing portable code, and persuading a large development team of varying levels of skill to write portable code as well.
Niklas Gustavsson presents Spotify's 2-layer services, and how the UNIX philosophy of composing components that does a single thing well works on a greater scale.
Yoni Goldberg discusses the many advantages that microservices can offer or has offered to the Gilt engineering team, as well as the challenges and how Gilt’s engineers solved these challenges.
Brad Greenlee talks about how Etsy have fostered their remote culture,the effort it took, and the work they still have to do. He shares their successes and failures and what they have learned.
Michael Bryzek presents lessons learned building an expansive microservice architecture at Gilt - an organization with 1500 git repositories and over 400 individual applications.
Amir Barylko shares from his experience being the owner of a new product, how to reach goals, how to fight the fear of not making it in time, and how to make sure Agile works for you.
Michael Norton keynotes on experimentation mindset, sharing experiments enabling Groupon to iterate on their products and cultivating an engineering culture through feedback and collaboration.
Adrian Cockcroft summarizes the differences and commonalities across some of the largest microservices deployments in production, showing how they are evolving.