Oracle Open World 2018 / Code One : MySQL 8.0 Document Store

MySQL 8.0
a Document Store with all the benefits of a transactional RDBMS

Frédéric Descamps - MySQL Community Manager - Oracle
3 / 130

Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purpose only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied up in
making purchasing decisions. The development, release and timing of any features or
functionality described for Oracle´s product remains at the sole discretion of Oracle.
Copyright @ 2018 Oracle and/or its affiliates. All rights reserved.
4 / 130

about me - http://about.me/lefred
Who am I ?
5 / 130

Frédéric Descamps
@lefred
MySQL Evangelist
Hacking MySQL since 3.23
devops believer
living in Belgium 🇧🇪
http://lefred.be

6 / 130

RDBMS & MySQL
Relational Databases
7 / 130

Data Integrity
8 / 130

Data Integrity
normalization
9 / 130

Data Integrity
normalization
constraints (foreign keys, ...)
10 / 130

Data Integrity
normalization
Atomicity, Consistency, Isolation, Durability
11 / 130

Data Integrity
normalization
ACID compliant
12 / 130

Data Integrity
normalization
ACID compliant
transactions
13 / 130

Data Integrity
normalization
ACID compliant
transactions
SQL
14 / 130

Data Integrity
normalization
ACID compliant
transactions
SQL
powerful query language
15 / 130

NoSQL & MySQL
NoSQL Databases
16 / 130

NoSQL or Document Store
Schemaless
17 / 130

Schemaless
no schema design, no normalization, no foreign keys, no data types, ...
18 / 130

Schemaless
very quick initial development
19 / 130

Schemaless
Flexible data structure
20 / 130

Schemaless
embedded arrays or objects
21 / 130

Schemaless
valid solution when natural data can´t be modelized optimaly into a relational
model
22 / 130

Schemaless
model
objects persistance without the use of any ORM - mapping object-oriented
23 / 130

Schemaless
model
JSON
24 / 130

Schemaless
model
JSON
close to frontend
25 / 130

Schemaless
model
JSON
close to frontend
native in JS
26 / 130

Schemaless
model
JSON
close to frontend
native in JS
easy to learn
27 / 130

How DBAs see data
28 / 130

How DBAs see data How Developers see data
{
"GNP" : 249704,
"Name" : "Belgium",
"government" : {
"GovernmentForm" :
"Constitutional Monarchy, Federation",
"HeadOfState" : "Philippe I"
},
"_id" : "BEL",
"IndepYear" : 1830,
"demographics" : {
"Population" : 10239000,
"LifeExpectancy" : 77.8000030517578
},
"geography" : {
"Region" : "Western Europe",
"SurfaceArea" : 30518,
"Continent" : "Europe"
}
}
29 / 130

What if there was a way to provide both SQL
and NoSQL on one stable platform that has
proven stability on well know technology with
a large Community and a diverse ecosystem ?
30 / 130

DBMS or NoSQL ?
31 / 130

DBMS or NoSQL ?
Why not both ?
32 / 130

The MySQL Document Store !
SQL is now optional !
33 / 130

SQL is now optional !
34 / 130

Developers:
[x] schemaless
[x] rapid prototying/simpler APIs
[x] document model
[x] transactions
Operations:
[x] performance
management/visibility
[x] robust replication, backup,
restore
[x] comprehensive tooling
ecosystem
[x] simpler application schema
upgrades
Business Owner:
[x] don't lose my data == ACID trx
[x] capture all my data =
extensible/schemaless
[x] product on schedule/time to
market = rapid developement
A solution for all
35 / 130

MySQL Document Store
the Solution
36 / 130

Built on
the MySQL
JSON Data
type and
Proven
MySQL
Server
Technology
Provides a schema flexible JSON Document Store
No SQL required
No need to define all possible attributes, tables, etc.
Uses new X DevAPI
Can leverage generated column to extract JSON values
into materialized columns that can be indexed for fast
SQL searches.
Document can be ~1GB
It's a column in a row of a table
It cannot exceed max_allowed_packet
Allows use of modern programming styles
No more embedded strings of SQL in your code
Easy to read
Also works with relational Tables
Proven MySQL Technology
37 / 130

X DevAPI Connectors for
C++, Java, .Net, Node.js, Python, PHP
working with Communities to help them supporting
it too
New MySQL Shell
Command Completion
Python, JavaScrips & SQL modes
Admin functions
New Util object
A new high-level session concept that can scale from
single MySQL Server to a multiple server environment
Non-blocking, asynchronous calls follow common
language patterns
Supports CRUD operations
38 / 130

X DevAPI
plenty of
sessions
during
Oracle
Code ONE
Developing Modern Applications with the MySQL
Document Store and NodeJS [HOL1706], Tue Oct 23,
11:15
Connector/J Beyond JDBC: The X DevAPI for Java and
MySQL as a Document Store [DEV6233], Tue Oct 23,
12:30
Develop Python Applications with MySQL
Connector/Python [DEV5957], Wed Oct 24, 9.00
Develop PHP Applivations with MySQL X Dev API
[DEV5981] - Wed Oct 24, 10.30
Python and the MySQL Document Store [DEV5959], Wed
Oct 24, 3:15pm
Node.js and the MySQL Document Store [DEV5986], Wed
Oct 24, 1.30pm
MySQL Connector/Node.js and X DevAPI [DEV5985], Thu
Oct 25, 10.00
39 / 130

Starting using MySQL DS in few minutes
00:05
40 / 130

MySQL Shell Info
00:05
41 / 130

Migration from MongoDB to MySQL DS
For this example, I will use the well known restaurants collection:
42 / 130

Migration from MongoDB to MySQL DS
For this example, I will use the well known restaurants collection:
We need to dump the data to a file and we will use MySQL Shell with the Python
interpreter to load the data.
43 / 130

Dump and load using MySQL Shell & Python
The following example is inspired by @datacharmer's work:
https://www.slideshare.net/datacharmer/mysql-documentstore

44 / 130

00:05
45 / 130

46 / 130

Even better since MySQL Shell 8.0.13
00:05
47 / 130

Let´s query
48 / 130

Let´s query
That´s too much records to show it here... let´s limit it
49 / 130

50 / 130

Some more examples
51 / 130

Some more examples
Let´s add a selection criteria:
52 / 130

Using IN...
53 / 130

Syntax slightly different than MongoDB
54 / 130

Syntax slightly different than MongoDB
> db.restaurants. nd({"cuisine": "French",
"borough": { $not: /^Manhattan/} },
{"_id":0, "name": 1,"cuisine": 1, "borough": 1}).limit(2)
{ "borough" : "Queens", "cuisine" : "French",
"name" : "La Baraka Restaurant" }
{ "borough" : "Queens", "cuisine" : "French",
"name" : "Air France Lounge" }
55 / 130

CRUD operations
56 / 130

CRUD operations for collections
Add a document
57 / 130

Add a document
collection.add({ name: 'fred', age: 42 })
.add({ name: 'dave', age: 23 })
.execute()
collection.add([
{ name: 'dimo', age: 50 },
{ name: 'kenny', age: 25 }
]).execute()
58 / 130

Modify a document
59 / 130

Modify a document
collection.modify('name = :name')
.bind('name', 'fred')
.set('age', 43)
.sort('name ASC')
.limit(1)
.execute()
collection.modify('name = :name')
.patch({ age: 43, active: false })
.sort('name DESC')
.limit(1)
.execute()
60 / 130

Remove a document
61 / 130

Remove a document
collection.remove('name = :name')
.sort('age ASC')
.limit(1)
.execute()
62 / 130

MySQL Document Store Objects Summary
63 / 130

Document Store Full ACID !
It relies on the proven MySQL InnoDB´s strength & robustness:
64 / 130

innodb_ ush_log_at_trx_commit = 1
65 / 130

innodb_doublewrite = ON
66 / 130

sync_binlog = 1
67 / 130

sync_binlog = 1
transaction_isolation = REPEATABLE-READ|READ-
COMMITTED|...
68 / 130

sync_binlog = 1
transaction_isolation = REPEATABLE-READ|READ-
COMMITTED|...
We do care about your data !
69 / 130

MySQL DS Full ACID - Transactions support
00:05
70 / 130

71 / 130

what about my old SQL ?
The hidden part of the iceberg
72 / 130

JSON datatype is behind the scene
native datatype (since 5.7.8)
73 / 130

JSON values are stored in MySQL tables using UTF8MB4
74 / 130

Conversion from "native" SQL types to JSON values
75 / 130

JSON manipulation functions (JSON_EXTRACT, JSON_KEYS, JSON_SEARCH,
JSON_TABLES, ...)
76 / 130

JSON_TABLES, ...)
Generated/virtual columns
77 / 130

JSON_TABLES, ...)
Indexing JSON data
78 / 130

JSON_TABLES, ...)
Indexing JSON data
Foreign Keys to JSON data
79 / 130

JSON_TABLES, ...)
Indexing JSON data
Foreign Keys to JSON data
SQL Views to JSON data
80 / 130

How does the MySQL Document Store work ?
81 / 130

What does a collection look like on the server ?
82 / 130

_id Every document has a unique identifier called the document
ID, which can be thought of as the equivalent of a table´s
primary key. The document ID value can be manually assigned
when adding a document. If no value is assigned, a document
ID is generated and assigned to the document automatically !
Use getDocumentId() or getDocumentIds() to
get _ids(s)

83 / 130

Mapping to SQL examples
createCollection('mycollection')
84 / 130

CREATE TABLE `test`.`mycoll` (
doc JSON,
_id VARCHAR(32)
GENERATED ALWAYS AS (doc->>'$._id') STORED
PRIMARY KEY
) CHARSET utf8mb4;
85 / 130

doc JSON,
_id VARCHAR(32)
PRIMARY KEY
) CHARSET utf8mb4;
mycollection.add({'test': 1234})
86 / 130

doc JSON,
_id VARCHAR(32)
PRIMARY KEY
) CHARSET utf8mb4;
mycollection.add({'test': 1234})
INSERT INTO `test`.`mycoll` (doc)
VALUES (
JSON_OBJECT('_id','663807fe367ee6114e0e5458bdac28bf',
'test',1234)
);
87 / 130

Mapping to SQL examples (2)
mycollection.find("test > 100")
88 / 130

Mapping to SQL examples (2)
mycollection.find("test > 100")
SELECT doc
FROM `test`.`mycoll`
WHERE (JSON_EXTRACT(doc,'$.test') > 100);
89 / 130

SQL and JSON Example
90 / 130

same as:
91 / 130

same as:
we can use it in SQL:
92 / 130

SQL and JSON Example (2): validation
93 / 130

94 / 130

95 / 130

SQL and JSON Example (3): explain
96 / 130

SQL and JSON Example (3): explain
97 / 130

SQL and JSON Example (4): add index
98 / 130

SQL and JSON Example (4): add index
99 / 130

Indexes in Document Store
It's also possible to create indexes without using SQL syntax:
100 / 130

Indexes in Document Store
It's also possible to create indexes without using SQL syntax:
101 / 130

SQL and JSON Example (5): arrays
102 / 130

103 / 130

104 / 130

105 / 130

NoSQL as SQL
JSON_TABLE
106 / 130

NoSQL as SQL (2)
JSON_TABLE
107 / 130

NoSQL as SQL - aggregation
108 / 130

Challenge: list the best restaurant of each type
of food and show the top 10, with the best one
first !

don't forget that all these restaurants are just JSON documents
109 / 130

NoSQL as SQL - aggregation (2)
110 / 130

111 / 130

112 / 130

SQL and NoSQL - JOINS
113 / 130

114 / 130

115 / 130

SQL and NoSQL - JOINS (2)
116 / 130

117 / 130

118 / 130

SQL and NoSQL - and back to JSON Document
119 / 130

NoSQL or SQL
120 / 130

MySQL Shell is for DBAs and Developers
00:05
121 / 130

MySQL Shell is for DBAs and Developers (2)
00:05
122 / 130

Tuesday
HOL1706 - Developing Modern
Applications with the MySQL
Document Store and Node.js
DEV6233 - Connector/J Beyond
JDBC: The X DevAPI for Java and
MySQL as a Document Store
Wednesday
DEV5957 - Develop Python
Application with MySQL
Connector/Python
DEV5981 - Develop PHP
Applications with MySQL X DevAPI
DEV5986 - Node.js and the MySQL
Document Store
DEV5959 - Python and the MySQL
Document Store
Thursday
DEV5985 - MySQL
Connector/Node.js and the X
DevAPI
More at the conference:
catch up on yesterday's sessions
PRO3056 - Introduction to the MySQL Document Store
HOL1703 - A Practical Introduction to the MySQL Document Store
123 / 130

what do I gain ?
Conclusion
124 / 130

schemaless
flexible data structure
easy to start (CRUD)
Conclusion
This is the best of the two worlds in one product !
Data integrity
ACID Compliant
Transactions
SQL
125 / 130

127 / 130

http://lefred.be/content/top-10-reasons-for-
nosql-with-mysql/
128 / 130

129 / 130

Thank you !
Any Questions ?
share your 💕 for MySQL on social media using @mysql #MySQL8isGreat
#OOW18
130 / 130

Oracle Open World 2018 / Code One : MySQL 8.0 Document Store

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Oracle Open World 2018 / Code One : MySQL 8.0 Document Store

Similar to Oracle Open World 2018 / Code One : MySQL 8.0 Document Store (20)

More from Frederic Descamps

More from Frederic Descamps (20)

Recently uploaded

Recently uploaded (20)

Oracle Open World 2018 / Code One : MySQL 8.0 Document Store