Talking head
Ruby On Ales 2014

This presentation, by Bryce Kerley, is licensed under a Creative Commons Attribution ShareAlike 3.0
80x15

Distributed systems are big, in every sense of the word. From the biggest social networks and search engines to the simplest web or iOS application, distributed software causes problems, stemming from its greatest feature: the system should continue working even when parts break. Client applications without network connections still want to capture data, backends with a failed service or two shouldn't break the entire application, and the app should still mostly work even when the big datacenter (you know the one) goes down. How do you grow a simple monolithic Rails app into a distributed system? What does it take to make your UI save data for a network connection later? How do you even test all this stuff?

Rated: Everyone
Viewed 505 times
Tags: There are no tags for this video.