Opal Perry talks about how Allstate is building new applications that are evolutions of their core business, and modernizing decades of legacy investment.
Joseph Andaverde provides insight on how asynchronous patterns - callbacks, promises, generators, and async/await - can be applied through simple yet pragmatic examples.
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.
Casey West talks about anti-patterns and corresponding best practices based on his experience building application infrastructure and platforms, as well as the applications which are deployed to them.
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.
Daniel Rolnick talks about the process Yodle went through adopting and deploying microservices, including database architectures and architectural patterns that emerged.
Rachel Reese talks about the lessons she has learned at Jet.com on their way to developing the platform and how they’ve schooled themselves on what works and what doesn't for F# and microservices.
Casey West uses twelve-factor app essay as a guide to discuss the do’s and dont’s of building and running containers, each factor providing an opportunity to consider avoiding certain anti-patterns.
Leonard Garvey and Louis Simoneau discuss how to decompose a monolith, architectural and integration patterns to avoid creating a monolith, and useful patterns and tools along the way.
Daniel Bryant talks about the 2016 edition of the seven deadly sins in building microservices, some of the anti-patterns in microservices along with tools for avoiding them.
Peter Bourgon presents some of the idioms, design patterns, and practices that have proven themselves developing successful, scalable, and sustainable code using Go.