Noriaki Tatsumi discusses building a microservices architecture on Spring Cloud that's reliable, resilient, and scalable.
Adam Krieger discusses why containers have an impact on the entire organization, not just the developers through scalability, confidence of isolation and the reduction of cycle time.
Mikey Cohen presents real examples of how gateway services, built on top of Netflix's Open source project, Zuul, are used in front of nearly all of Netflix's consumer facing traffic
Will Ballard explains how small teams turning into large teams do more than change size-they change structure and add policies aimed at preventing mistakes rather than capturing the best outcomes.
Paul Sears discusses the decisions to be made and questions asked when establishing the architecture and technologies to be used for a web application that scales and can adapt to change.
Ian Fyfe discusses the different options for implementing speed-of-thought business analytics and machine learning tools directly on top of Hadoop.
Alois Reitbauer discusses challenges and solutions on the organizational, development and operational side, deploying faster, decoupling a monolith without breaking the logic and dynamically scaling.
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.
Alexander Grosse discusses the principles behind building successful organizations that are growing with examples from SoundCloud and Twitter.
Jay Marshall and Vic Iglesias talk about how GCP was built for the enterprise, enabling users to deploy their applications on the same infrastructure Google uses for search, YouTube or GMail.
Anthony McCulley describes The Home Depot’s first year with Cloud Foundry, adopting the platform, scaling to hundreds of developers across multiple data centers, and mistakes made along the way.