Amar Sharma talks about NBC Universal Microservices infrastructure and how the new way they approach software development has equipped them to make better decisions about product investment.
Justin Smith discusses credential hygiene in distributed systems, covering topics such as key encrypting keys, hardware security modules, and promising advances in muti-party computation.
Jon Harding discusses design patterns and best practices to create scalable applications, build processes to prepare for production and tips to prepare for transitioning to Angular 2.
Todd Montgomery investigates whether WebSockets, HTTP/2, Reactive Streams and microservices can deliver the high scalability, resiliency, and ease of development promised.
John Billings talks about winning over those skeptical about the benefits of microservices along with tips on caching, failure, interface changes, etc. for building a distributed system architecture.
Aysylu Greenberg revisits some features of modern distributed systems and shows three architectural patterns, their application, and reference papers that are relevant to today's distributed systems.
Peter Lawrey discusses the differences between microservices and monolith architectures, their relative benefits and disadvantages, patterns and strategies implementing low latency microservices.
Philip Glebow discusses patterns, tools and processes used by Gap for integration, messaging, data, and scaling on Cloud Foundry, sharing lessons learned and plans for the future.
Steve Green discusses balancing emergent designs with intentional planning, common architecture principles, guidelines for measuring good architecture, and an evaluation of agile techniques.
Daniel Rolnick talks about the process Yodle went through adopting and deploying microservices, including database architectures and architectural patterns that emerged.
Alan Ho and Sandeep Murusupalli discuss the right type of protection (OAuth/Throttling) and monitoring (e.g. bot monitoring) needed to be put in place to properly manage microservices.
Sebastian von Conrad and James Ross explain how to use event sourcing in order to keep the cost of change lower.