Have you seen the latest updates for traditional RDBNS lately? It's insane. They are all catching up and won't be left out. While all NoSQL stores are proposing SQL, all RDMS are proposing top notch JSON support. And it does not stop there. Latest PostgreSQL version have added new scalability features like table partitioning, query parallelism, pub/sub framework, a new quorum system for data sync. They have also improved their window functions for better time series queryability. And as it happens, we are using some of these new functionalities at Clever Cloud. In this talk I will showcase some of them to try to convince you that PostgreSQL is the new NoSQL. talk is recorded here: https://www.youtube.com/watch?v=t8-BQjWJFKw https://dvbe18.confinabox.com/talk/BLA-3308/PostgreSQL_is_the_new_NoSQL

1. PostgreSQL is the new
NoSQL
QUENTIN ADAM
CEO @ CLEVER CLOUD
@WAXZCE ON TWITTER
AT DEVOXX 2018

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

3. https://www.youtube.com/c/MaiaMater “Interviews en toge”
https://www.youtube.com/c/clevercloudplatform
or search “Quentin ADAM”

5. 💡☁️

6. Clever Cloud
💡☁️

7. Git push
It’s free to try it out

8. Deploy
&
Application sustainability
European Cloud & on premises

9. Data @ Clever Cloud

10. Data have gotten big

11. noSQL and big data world

12. CAP theorem

13. Make your choices
• Transactions
• Consistency
• Schema
• Constraint
• Event flow
• Request capabilities
• Scale (volume, numbers…)
• Indexes
• ACL
• …

14. Rush to the noSQL landscape

15. Store

16. And we discover some comfort
on the old RDBMS

17. Request/Analyze

18. SQL

19. SQL-ish

20. Luckily someone is improving our home

21. Postgres story
• SINCE 1995
• First name Ingres

22. Popularity

23. Playlist management app, multiple
backend, playlist history
To do
example

24. entities
• user management
• Playlists
• Tracks history (deezer, spotify, soundcloud)

25. Track data is heterogeneous

26. We need schemaless

27. Arbitrary data depth

28. External data is
already json

29. BTW, why do not use
noSQL?

30. “I need unique user on email”

31. constraints

32. “which Tracks are played at
8pm to 9pm week days?”

33. Complex data
exploratory is
hard

34. “… in paris area”

35. Complex data
exploratory is
hard

36. “… by male users”

37. Need some
relationships in your
data store?

38. “…order by..”
“…UI need pagination…”

39. SQL have been done to show
data
Show data VS Analitycs

40. So we are on PG for good reasons

41. Let’s create our tracks table

42. Uuid as primary key
& no serial

43. “we have 2000000 users on our
product”
http://www.my-platform.com/users-creation-
confirm/42?valid_key=jgqsdkfhqksdjfhkjsdhf2342345

44. Using it to count things >_<

45. Same id for various entities on
your database <_>

46. What is my ID?
Generate it on the code level

47. Put a name on things
Computer science problem

48. Blog article by the awesome @clementd (former Clever Cloud CTO)
https://www.clever-cloud.com/blog/engineering/2015/05/20/why-auto-increment-is-a-terrible-idea/

49. Let’s create our tracks table

50. USE enum

51. USE timestamptz

52. Let’s create our tracks table

53. Postgres have two json type
• Json: text input, parsed each time we need it
• Jsonb: decomposed binary format (ie: almost already parsed)
TLDR: use jsonb

54. Json/jsonb data on your DB

55. Let’s create our tracks table

56. Request json

57. Or test existence

58. Use sql function on it

59. Plenty of capacity for json • Array length, data
manipulation, filters,
jsonpath, prettyfier

60. Temporal function with pgsql

61. Count(*) on nosql is hard?
=> Use SQL

62. Index

63. choose db (and version)

64. ORM is not your best friend here, sadly

65. Jdbc drivers

66. Workaround

67. Workaround

68. Manage it like regular json in
your code

69. Data is going big and
query slow…

70. Use parallel queries: split queries to multiple CPU
• max_parallel_workers & max_parallel_workers_per_gather +
dynamic_shared_memory_type in configuration

71. Hash & Scan improved by GPU
• PG-Storm http://heterodb.github.io/pg-strom/
• PG extension with CUDA (nvidia chip)
• Useful for Hash and Scan
(I never used it)

72. Am I locked on only one node? Clustering?

73. Master/slave
Using live replication

74. Split request on your
code

75. Or use pgpool
Able to make requests navigation

76. Use replica for specific
purpose
BI for example, keep production DB stable

77. Logic Replication (partial)
Since 10

78. Pub/Sub
• Notify
• Listen (have to be
supported by the
driver)

79. Quorum
Since 10
(I never used it yet)

80. Foreign Data Wrapper

81. Request Postgres using Postgres

82. Table sharding
Since 10/11
(I never used it yet)
https://pgdash.io/blog/postgres-11-sharding.html

83. Table sharding
Since 10/11
(I never used it yet)
https://pgdash.io/blog/postgres-11-sharding.html

84. Table sharding
Since 10/11
(I never used it yet)
https://pgdash.io/blog/postgres-11-sharding.html

85. Since 10/11
(I never used it yet)
Foreign
Data
Wrapper
(posgres)
Table
Sharding
Split a
table
accros
servers

86. DB stability is driven
by predictability
Use proxy for your DB, as PG bouncer

87. Get metrics, learn, improve
• http://dalibo.github.io/
powa/

88. Free dev plan on Clever Cloud

89. One click launch

90. PG 11.1 with auto update

91. I’m @waxzce on twitter
Give CLEVER-CLOUD.COM a try
Free credits coupon (both work):
💡☁️🦋
devoxx_be_18
Thx for listening