NoSQL databases are every where and they are here to stay. For a successful scalable web application it is vital to understand capabilities of NoSQL databases. Also relational databases are not dead and they will not be. Understanding abilities of each, would help making better architectural decisions. Hybrid database solutions could use bests of the both worlds. We would go in to the important decision making factors for each.

1. Polyglot
Persistence

2. Majid Fatemian
R E D V E N T U R E S
@majidfn

3. Relational Non-Relational Key-Value Big Data

4. Application
Relational

5. Application
Relational Relational Non-Relational

6. Relational

7. BIG
DATA

8. Capture
Search
Storage
Q u e r y
Privacy
Visualize
Analysis

9. Non-Relational

10. 1 2 3
Non-Relational Cluster Schemaless

11. 2 x
1 x
1 x

13. 2011
2012
2013
2014

14. 2011
2012
2013
2014

16. Application

17. ACID
Normalized
{Consistency
Relational

18. Player ID Map ID Difficulty Score
1000 223 E 5
2000 673 H 4.5
1000 451 M 4
2000 980 H 3
Activity
Player ID Name Location
1000 John US
2000 Catherine CA
3000 Paul CA
4000 Kylee US
Profile

19. Replication
Fault Tolerance
Availability
{Relational

20. OPs / DBAs
Tools
Devs{DevOps
Relational

21. 2011
2012
2013
2014

24. Scalability
Relational

25. Distribution
Relational
Data C
Data B
Data A
Data Access Layer

26. Schema
Relational
{
player_id: 1234,
* level: 40,
* duration: 75,
* activity: activity,
game_id: 4001,
platform: WiiU,
difficulty_level: medium,
repetition: 178,
score: 450,
endurance:3
}
{
player_id: 1234,
level: 12,
duration: 120,
activity: activity
}

27. Total
Detailed
stats
stats
Players Profiles
Individual Activities
Aggregated
stats
Categorized

28. ACID
Transaction
Partitioning
Replication
Tools
OPs
Data Volume
Fixed Schema
Scale Up
Manual Sharding
+ -

29. NoSQL
...

30. mongoDB
1 2 3
OPs Devs Community

31. Schema-less
Non-Relational
player_id: 1234,
* level: 40,
* duration: 75,
* activity: activity,
game_id: 4001,
platform: WiiU,
difficulty_level: 2,
repetition: 178,
score: 450,
endurance:3
player_id: 1234,
level: 75,
duration: 120,
activity: activity

32. Scalability
Non-Relational

33. Scalability
Non-Relational
+

34. Sharding
Non-Relational
Data A
{key}

35. Sharding
Non-Relational
Data A
A
Data B
B
Data C
C
{key}

36. Map/Reduce
Non-Relational
Query
K, V
K,V1 K,V2 K,V3

37. Map/Reduce
Non-Relational
Map
K,V1 K,V2 K,V3

38. Map/Reduce
Non-Relational
Result
ReduceMap
K,V1 K,V2 K,V3

39. Denormalized
Non-Relationalread /
}write
Disk Space

40. Player ID Map ID Difficulty Score
1000 223 E 5
2000 673 H 4.5
1000 451 M 4
2000 980 H 3
Activity
Player ID Name Location
1000 John US
2000 Catherine CA
3000 Paul CA
4000 Kylee US
Profile

41. {Name: John, game:1, activity: Mission01, Score: 1245}
{Name: John, game:3, activity: Mission04, score: 5431}
{Name: John, game:1, activity: Mission01, Score: 1245}

42. Data Model
Non-RelationalQuery
Aggregation
}

43. Eventual-
Consistency
Non-Relational
X2
W
X1 X1
X2

44. Eventual-
Consistency
Non-Relational
X2
W
X1 X1
R
X1
X2

45. Eventual-
Consistency
Non-Relational
X2
W
X2
X2
R
X2
X2

46. Balancer
Non-Relational

47. Balancer
Non-Relational
+

48. Balancer
Non-Relational

49. Non-Relational
Resilience
A B C

50. Non-Relational
Resilience
A C

51. Locking
Non-RelationalDB Level (2.2)
}Document Level (3.x)

52. Backup
Non-Relational
Point-in-time

53. Denormalized data
Disk Space
Expertise
Complex Querying
Eventual Consistency
Resource Usage
DB-Level Locking
-
Schema-Less
Aggregated Data
Large Scale Data
Sharding
Map/Reduce
Memory Storage
Journaling
+

54. Random Profile
Search
(1M)
Full History
Retrieval
(6M)
Insert
(6M)
Aggregation
Map/Reduce
(6M)
0
0.003
0.005
0.008
0.01
MySQL
MongoDB

55. Persistence
Polyglot

56. Players Profile
Leaderboards
Activity Details
Relational Data
Schema-less
Sharding

57. Total Sum
Activity 1
Activity n
Activity m
……

58. Shard1
Shard2
Config

59. Data Access Layer
Application

60. The
Challenge

61. Inconsistency1

62. Data Access Layer
W
Pending
Commit
2-Phase

63. Data Access Layer
Pending
W
Commit
2-Phase

64. Data Access Layer
Done
Commit
2-Phase

65. 2 Latency
vs. Consistency

66. Operations3 Exponential complexity

67. Availability4 Plan for failure

68. Data Access Layer

69. Data Access Layer

70. Data Access Layer

71. Data Integrity5 Backward compatibility

72. Unit
{TEST Integration
Functional

73. Data Migration6

75. Profile
History }
{
profile:
{
GUID:…,
platform:
{
name:’xbox’,
xuid:…
}
},
activity:…,
duration:…,
datetime:…
}
3rd Party

76. 1 One-Shot Migration
4 hours !!
Live !!
2 Profile versioning

77. V
+1
1

78. V
+1
1

79. V
+1
2

81. Final
Results

82. Scalability
2011 2012 2013 2014

83. 9x response time

84. 3 years uptime

85. Go Hybrid!
Thoughtfully
>

86. Thank
YOU!
@majidfn

87. References
Polyglot Persistence
NoSQL Distilled