What do the webscale nosql craze and the meltdown attack have in common ?

1. TUGA ITSUMMER EDITION
LISBON, JULY 19-21, 2018

2. THANK YOU TO OUR SPONSORS
GOLD SPONSOR
TUGA BEER SPONSOR
SILVER SPONSOR
SWAG SPONSOR

3. from webscale
to meltdown
Carlos Morgado
Principal Engineer
today @ here
3

4. act 1

5. it was 2007
Rihanna was singing about her
umbrella and global finance was
about to collapse
5

6. “but this database doesn’t scale”
“schema is cramping my style”

7. “i’ll invent a
new
hyper scalable
database!”

12. https://stackoverflow.com/questions/2623852/why-are-joins-bad-when-considering-scalability

14. https://stackoverflow.com/a/17459488

18. “To recap: MongoDB is neither AP nor CP.
The defaults can cause significant loss of
acknowledged writes. The strongest
consistency offered has bugs which cause
false acknowledgements, and even if they’re
fixed, doesn’t prevent false failures.”
— Aphyr, 2013

20. act 2

21. on a parallel
story

22. Intel was still recovering from the
itanium fuelled madness and
core2duo cpus were being shipped

24. © SEGA. SEGA, the SEGA logo and SONIC THE HEDGEHOG are either registered trademarks or trademarks of SEGA Holdings Co., Ltd. or its affiliates.

26. http://coeunitedparallelprocessing.blogspot.pt/2014/03/superpipeline-and-superscalar.html

27. LD A,1
M M M R
LD B,2
M M M R
LD C,3 W W M M M R
LD D,4 W W M M M R
ADD E,A,C W W W W ALU R
ADD F,B,D W W W W ALU R
ADD G,A,B W W W W ALU
1 2 3 4 5 6 7 8

28. LD A,1
M M M R
LD B,2
M M M R
LD C,3 W W M M M R
LD D,4 W W M M M R
ADD E,A,C W W W W ALU R
ADD F,B,D W W W W ALU R
ADD G,A,B ALU R
1 2 3 4 5 6 7 8

29. LD A,1
M M R
LD B,2
M M R
LD C,3 W M M R
JZ +2, C W W W EX R
ST D,0 W W W ALU ?
SUB E,A,B W W W ALU R
ST 10,E W W W M R
1 2 3 4 5 6 7 8

30. LD A,1
M M R
LD B,2
M M R
LD C,3 W M M R
JZ +2, C W W W EX R
ST D,0 ALU ? R
SUB E,A,B ALU ? R
ST 10,E W W M R
1 2 3 4 5 6 7 8

31. LD B, [T] M M W W W W W SEGV
SHL B, 8 W W ALU ?
LD C,
[P + B]
W W M M ?
1 2 3 4 5 6 7 8

32. act 3

33. webscale ? spectre ? meltdown ?
what ?

34. Distributed systems are hard

35. Fast distributed systems are
even harder

36. and error prone even if you know
what you are doing

37. Fundamental design flaws

38. Implementation bugs

39. Unpredicted behaviours

40. Everything is a distributed system

41. property testing

42. chaos testing

43. correctness proofs

44. talkdesk.com
linkedin.com/company/talkdesk
twitter.com/talkdesk
facebook.com/talkdesk
Tkx! Questions ?
@chbm

45. PLEASE FILL IN THE
EVALUATION FORM.
YOUR OPINION IS
IMPORTANT!

46. THANK YOU TO OUR SPONSORS
GOLD SPONSOR
TUGA BEER SPONSOR
SILVER SPONSOR
SWAG SPONSOR