Simon Chan shares the on-going challenges, the design dilemma and the steps to be taken when building customized large-scale predictive ML applications on a ML SaaS platform.
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.
Adrian Trenaman provides detailed examples of how HBC Digital has used Docker and what aspects of the technology haven't panned out as they thought they would.
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.
Thomissa Comellas shares her experiences developing and rolling out new Disaster Recovery Testing techniques at Dropbox. Tammy Butow shares how her team runs DRTs and has implemented the techniques.
Daniel Rolnick talks about the process Yodle went through adopting and deploying microservices, including database architectures and architectural patterns that emerged.
Spencer Chan overviews Quora's architecture that allows them to share the majority of their application code across their Android, iOS and web apps, discussing challenges and benefits.
Manny Pelarinos talks about the tension of optimizing APIs for different experiences, while supporting hundreds of endpoints and many web and mobile applications at scale.
Caitie McCaffrey discusses the strategies for proving a correct system and less strenuous methods of testing, which can help increase our confidence that a system is doing the right thing.
Rossen Stoyanchev discusses what reactive programming is all about and tries to make sense of the transition from traditional application development to reactive programming.