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.
Links
- Recursion
- Eventual consistency
- Pubsub
- RethinkDB
- Event sourcing
- React native
- Android studio
- Mnesia - a "distributed, soft real-time database management system" written in Erlang
- Dirty reads and writes
- Websockets
- QUIC
- UDP
- TCP
- WebRTC
- NAT
- HTTP live streaming
- Lars' ElixirConf talk
- Zoom H4
- Zoom H4n pro
Quotes
- Working with systems and feeling the pain
- Coping with system design
- Eventually consistent, on a good day
- Eventually sourced
- A disappointment to work with
- Your internal representation of the user
- This is the shape of the data, deal with it
- 1.5 source of thruths
- Oh, it's an optimist
- I don't like optimists at all
- Optimist databases
- Within its working well-window
- Outside of the working well-window
- A crash of servers
- Bad connections over long distances
- I don't do math