Designing Data-Intensive Applications – Lost Updates and Write Skew

1

Introduction

00:00 • 2min

2

How to Prevent Lost Updates

02:04 • 2min

3

How to Stop Stepshot Isolation From Getting Worse

04:15 • 3min

4

Application Development

07:15 • 2min

5

Databases - Cursor Stability and Single Threading

09:23 • 2min

6

Falling Behind Can Effectively Mean Stopping a Database Query

11:04 • 3min

7

Is There a Way to Lock the Front Page?

14:07 • 3min

8

Is There a Problem With Lost Updates?

16:48 • 4min

9

Is the Transaction ID on the Data Higher Than Transaction ID?

20:29 • 2min

10

Is NODB the Default Storage?

22:04 • 2min

11

Is Your Database Not Supporting Transactions?

23:49 • 2min

12

Orms - What's the Difference?

25:44 • 5min

13

Code Blocks Slash Review - Got Him Before Jay Z?

30:16 • 3min

14

All Right. Alan's Streak Is Off to a Great Start

33:34 • 3min

15

Need a Taxi?

36:04 • 3min

16

What's the Number Two Answer on the Board?

38:39 • 3min

17

What Is the Best Way to Get Away From the Streets?

41:40 • 3min

18

What if You Can't Have Two Records in the Same Table?

44:45 • 2min

19

The Problem of Overwriting a Value to the Same Record

46:42 • 4min

20

Stack Overflow Interviews

51:03 • 4min

21

Is Serializable Isolation the Best Option?

54:41 • 6min

22

The Scheduling Table Can Help You With This Problem

01:00:38 • 4min

23

Is This a Last Resort?

01:04:20 • 2min

24

Docker Build Kit

01:05:56 • 5min

25

Do You Run Into Context Problems?

01:11:07 • 2min

26

Binding a Docker Secret

01:12:45 • 2min

27

Docker Build Kits

01:14:31 • 4min

28

Kubernetes Debug Containers - Ephemeral Debug Container

01:18:18 • 6min