DATA DURABILITY
WITH
SCHEMALESS
DATABASE
QUENTIN ADAM - @WAXZCE
WHO I AM ?
CEO of Clever
Cloud
@waxzce on
twitter
WE ALL WANT TO USE CUTTING
EDGE TECHNOLOGIES
OR MAYBE WE NEED SOME NEW DB FOR
OUR APPS
NOSQL
CHANGE THE DATA WORLD FOREVER
DOCUMENTS + SCHEMALESS
IS GREAT
SURVEY
DID YOU THINK ABOUT DATA
DURABILITY?
NULLPOINTEREXCEPTION, UNDEFINED,
NULL IS NOT DEFINED….
HUM… SEEMS YOUR DOCUMENTS
ARE NOT SIMILAR
PUT LOT OF IF/ELSE IN YOUR
CODE ?
DO WE HAVE TO UPDATE ALL THE
DOCS IF WE CHANGE THE
PATTERN ?
SEARCH FOR A BETTER SOLUTION
FIRST :
VERSION ALL THE DOCUMENTS
LIKE THIS :
{
id : […],
pattern : [… (usually a string)],
version : [… integer],
[…]
}
SECOND :
PROXY ALL DATABASE CALL IN
YOUR CODE
BUILD A PATTERN UPDATER
DATA FLOW
database
Entering
data
proxy
Update
data from
version 2
to
version 3
Update
from
version 3
to
version 4
Out of
d...
WHEN YOU DO
SOMETHING
UGLY, DO IT IN
A SPECIFIC
PART OF YOUR
CODE
EASY TO FIND UGLY
CODE
ALL DATA MODIFICATIONS
ARE DOCUMENTED
DO NOT IMPACT ALL YOUR
CODE
DATA DURABILITY
IS SOMETHING
MADE BY DESIGN
AT THE BEGINNING
OF THE PROJECT
WE STILL LEARNING FOR
NOSQL GOOD PRACTICES
USE IT!
IT’S REALLY GREAT 
I’m @waxzce on twitter
I’m the CEO of
A PaaS provider, give it a try
;-)
THX FOR LISTENING
& QUESTIONS TIME
Upcoming SlideShare
Loading in …5
×

Data durability with schemaless database - Breizhcamp version

1,234 views

Published on

Published in: Technology

Data durability with schemaless database - Breizhcamp version

  1. 1. DATA DURABILITY WITH SCHEMALESS DATABASE QUENTIN ADAM - @WAXZCE
  2. 2. WHO I AM ? CEO of Clever Cloud @waxzce on twitter
  3. 3. WE ALL WANT TO USE CUTTING EDGE TECHNOLOGIES
  4. 4. OR MAYBE WE NEED SOME NEW DB FOR OUR APPS
  5. 5. NOSQL CHANGE THE DATA WORLD FOREVER
  6. 6. DOCUMENTS + SCHEMALESS IS GREAT
  7. 7. SURVEY
  8. 8. DID YOU THINK ABOUT DATA DURABILITY?
  9. 9. NULLPOINTEREXCEPTION, UNDEFINED, NULL IS NOT DEFINED….
  10. 10. HUM… SEEMS YOUR DOCUMENTS ARE NOT SIMILAR
  11. 11. PUT LOT OF IF/ELSE IN YOUR CODE ?
  12. 12. DO WE HAVE TO UPDATE ALL THE DOCS IF WE CHANGE THE PATTERN ?
  13. 13. SEARCH FOR A BETTER SOLUTION
  14. 14. FIRST : VERSION ALL THE DOCUMENTS
  15. 15. LIKE THIS : { id : […], pattern : [… (usually a string)], version : [… integer], […] }
  16. 16. SECOND : PROXY ALL DATABASE CALL IN YOUR CODE
  17. 17. BUILD A PATTERN UPDATER
  18. 18. DATA FLOW database Entering data proxy Update data from version 2 to version 3 Update from version 3 to version 4 Out of data proxy Code use version 4, no question 
  19. 19. WHEN YOU DO SOMETHING UGLY, DO IT IN A SPECIFIC PART OF YOUR CODE
  20. 20. EASY TO FIND UGLY CODE
  21. 21. ALL DATA MODIFICATIONS ARE DOCUMENTED
  22. 22. DO NOT IMPACT ALL YOUR CODE
  23. 23. DATA DURABILITY IS SOMETHING MADE BY DESIGN AT THE BEGINNING OF THE PROJECT
  24. 24. WE STILL LEARNING FOR NOSQL GOOD PRACTICES
  25. 25. USE IT! IT’S REALLY GREAT 
  26. 26. I’m @waxzce on twitter I’m the CEO of A PaaS provider, give it a try ;-) THX FOR LISTENING & QUESTIONS TIME

×