About System Design

Did they do design, or did they just do a system?Distributed systems are hard in many ways. Andreas describes a system communicating between backends and mobile phones in exciting ways with many exciting possibilities for errors. Like data format changes, loss of messages, having 1.5 source of truths, and of course ordering.In certain cases, nobody likes an optimist.The discussion then moves to discuss the working well-windows for various networking solutions, before diving into WebRTC and finishing up with the various dangers of auto.LinksRecursionEventual consistencyPubsubRethinkDBEvent sourcingReact nativeAndroid studioMnesia - a "distributed, soft real-time database management system" written in ErlangDirty reads and writesWebsocketsQUICUDPTCPWebRTCNATHTTP live streamingLars' ElixirConf talkZoom H4Zoom H4n proQuotesWorking with systems and feeling the pain Coping with system designEventually consistent, on a good dayEventually sourcedA disappointment to work withYour internal representation of the userThis is the shape of the data, deal with it1.5 source of thruthsOh, it's an optimistI don't like optimists at allOptimist databasesWithin its working well-windowOutside of the working well-windowA crash of serversBad connections over long distancesI don't do math