As web developers, there is a demand for us to build scalable web applications that are always on and resistant to failure.
If we're lazy or uninformed, we'll push this problem to the people responsible for operations (even if it's ourselves) and inevitably, it will come back to bite us.
We must make decisions up-front on how we are going to model and store the data we produce from our web applications.
The trade-off of having a highly available, scalable, fault-tolerant system requires us to think differently about modelling, and how we present data to our users.
The compromise for availability is known as "eventual consistency", and it can be intimidating.
We'll talk about how we already deal with eventual consistency in the real world, how it is resolved in web applications, and how it is our responsibility as developers to encode the world we live in.
Sign in to add slides, notes or videos to this session