This document discusses the advantages of PostgreSQL over NoSQL databases for certain use cases. It describes a playlist management app that tracks user playlists and music histories across different services. It argues that PostgreSQL is better suited than NoSQL because it supports relationships in data, complex queries, ACID transactions, and leverages the power of SQL. Choosing a database depends on architecture needs rather than preferences, and the author encourages trying PostgreSQL before making a decision.

1. WHY POSTGRES
SQL DESERVE
NOSQL FAN
RESPECT QUENTIN ADAM
@WAXZCE

2. Quentin ADAM from the Clever Cloud
@waxzce on twitter – github- soundcloud – instagram ….
WHO AM I ?

3. MY DAY TO DAY WORK :
CLEVER CLOUD, MAKE YOUR
APP RUN ALL THE TIME

4. And learn a lot of things about your code, apps, and good/bad design…
KEEP YOUR APPS ONLINE. MADE WITH
NODE.JS, SCALA, JAVA, RUBY, PHP,
PYTHON, GO…

5. AND LEARN A LOT OF THINGS ABOUT
YOUR CODE, APPS, AND GOOD/BAD
DESIGN…

6. NOSQL WORLD

8. SOME OF THE COOL THINGS
• ACID or not
• Schemaless or not
• Concurrent writing or not
• Consistent or eventually consistent
• HA or not
• …

9. THINK ABOUT THE DATA
STORAGE

10. LET’S EXAMPLE

11. PLAYLIST
MANAGEMENT APP,
MULTIPLE
BACKEND,
PLAYLIST HISTORY
TO DO

12. ENTITIES
• user management
• Playlists
• Tracks history (deezer, spotify, soundcloud)

13. TRACK DATA IS
HETEROGENEOUS

14. Use nosql
WE NEED SCHEMALESS

15. ARBITRARY DATA DEPTH

16. EXTERNAL DATA IS ALREADY JSON

17. “I NEED
UNIQUE
USER ON
EMAIL”

18. CONSTRAINTS

19. “WHICH
TRACKS ARE
PLAYED AT
8PM TO 9PM
WEEK DAYS?”

20. COMPLEX DATA
EXPLORATORY IS HARD

21. “… IN PARIS
AREA”

22. COMPLEX DATA
EXPLORATORY IS HARD

23. “… BY MALE
USERS”

24. NEED SOME RELATIONSHIPS IN YOUR
DATA STORE?

25. “…ORDER
BY..”
“…UI NEED
PAGINATION
…”

26. WE
ALREADY
KNOW ALL
OF THESE

27. POSTGRESQL

28. LET’S CREATE OUR TRACKS
TABLE

29. UUID AS
PRIMARY
KEY
& NO
SERIAL

30. “WE HAVE 2000000 USERS
ON OUR PRODUCT”
http://www.my-platform.com/users-creation-confirm/42
?valid_key=jgqsdkfhqksdjfhkjsdhf2342345

31. SAME ID FOR VARIOUS ENTITIES
ON YOUR DATABASE

32. LET’S CREATE OUR TRACKS
TABLE

33. USE ENUM

34. USE TIMESTAMPTZ

35. LET’S CREATE OUR TRACKS
TABLE

36. NATIVE JSON & JSONB TYPE

37. LET’S CREATE OUR TRACKS
TABLE

38. THEN EMBRACE SQL POWER

39. *WITH REAL DATABASE LIKE
POSTGRE SQL

40. REQUEST JSON

41. USE SQL FUNCTION ON IT

42. TEMPORAL FUNCTION WITH
PGSQL

43. COUNT(*) ON NOSQL?

44. GEO BASED REQUEST?

45. INDEX

46. TRANSACTIONS

47. ACID

48. BOOTSTRAPPING?

49. “MY PLAIN
OLD SQL IS
SO
POWERFUL?
”

50. CHOOSE DB (AND VERSION)

51. KILL THE ORM

52. JDBC DRIVERS

53. WORKAROUND

54. WORKAROUND

55. MANAGE IT LIKE REGULAR
JSON IN YOUR CODE

56. FREE YOUR MIND ABOUT
DATASTORE + DRIVER ACCESS

57. “SO PGSQL
IS BETTER
THAN
MONGO?”

58. ATOMICITY OF CHANGE
INSIDE A JSON

59. CONCURRENT INSERT

60. SHARDING & REPLICA

61. HIGH AVAILABILITY

62. CHOOSE A
DATASTORE IS
REAL
ARCHITECTURE
JOB

63. TRY IT
BEFORE :-)

64. FREE DEV
PLAN ON
CLEVER
CLOUD

65. ONE CLICK LAUNCH

66. I’m @waxzce on twitter
I’m the CEO of
A PaaS provider, give it a try
;-)
THX FOR LISTENING
& QUESTIONS TIME
Clever Cloud coupon : devoxx15roxx