NoSQL Design

1. NoSQL Design
Diego Pacheco

3. Design

4. Requirements

6. Architecture is all about Tradeoffs
❏ Given a USE CASE:
❏ What Benefits?
❏ What issues it has?
❏ What dependencies?
❏ What risks?
❏ How we improve it?
❏ How we validate it?
❏ How we know we are right?
❏ Build VS Buy Analysis
❏ Open Source VS Paid software
❏ How much up to front work?

9. SQL

10. The universe as we know...

12. The universe as we know...
=
=

13. The universe as we know...

14. Declarative: I don't care, just get it done....

15. Relational abuse !!!

16. NoSQL

17. Much Bigger Universe...

18. a Different universe...

19. Different ways do ASK and ANSWER questions....
❏ NoSQL WAY
❏ “No Tables”
❏ “No Joins”
❏ “No ACID”
❏ Different “schema”
❏ More Data Structures
❏ I need to know what I'm m doing.
❏ What do I want todo?
❏ What Access patterns do I have?
❏ I need fix problem in “parts”.
❏ Looks like much more work... (yes)
❏ ... Much better Performance / Scalability
❏ ... “RIGHT DESIGN”
❏ What about integrity?
❏ Be my guest ! LOL
❏ Looks like we “strip” the “DB” and we are
doing all the work on APP side? YES!
❏ Seriously? YES!

24. CAP: Pick 1, forget the P.

25. ES/CQRS

26. #1 Reason why we need ES == Microservices

28. No Places, RAW Events.

29. Immutability == Append ONLY

30. Segregation == Scalability

31. ES
Persists RAW
EVENTS.
When there are
mutations, NEW
events are created.

32. CQRS
IT's about scaling
READ and
WRITES, basically
in different
RELATIONAL
DBS.

33. CQRS / ES :: Design

34. CQRS / ES :: Design

35. KAFKA

38. Kafka: Numbers at LinkedIN 2019/Q1

39. Kafka: As ES Solution

40. Kafka

42. Kafka

43. Kafka

44. Kafka: Other use Cases

45. Lambda / Kappa Architecture

46. Kafka: What Platform can do!

47. Streaming:: Brave new world!

48. REDIS

49. Redis

50. Stack Overflow 2019 Numbers

51. Use Cases

52. Data Structures

53. Keys Modeling

55. Books

57. NoSQL Design
Diego Pacheco