Oracle Code Roma: NoSQL + SQL = MySQL

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 @ 2019 Oracle and/or its affiliates. All rights reserved.
3 / 100

about me - http://about.me/lefred
Who am I ?
4 / 100

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

5 / 100

MySQL
a Document Store with all the benefits of a RDBMS
6 / 100

Why ?
Developers don´t really like SQL

7 / 100

Why ?
SQL can be complicated and slows down the initial development
8 / 100

easy operations
What do developers want ?
9 / 100

Use Objects / Documents
Developers want just to use objects
10 / 100

that´s why they usually love what DBAs hate the most ORMs !).
11 / 100

They want to deal with these objects easily (CRUD operations) and they don´t want to
think about schema design (slows down the initial development process).
12 / 100

They want to deal with these objects easily (CRUD operations) and they don´t want to
think about schema design (slows down the initial development process).
But they also want to keep their data safe and use transactions.
13 / 100

RDBMS & MySQL
Relational Databases
14 / 100

Data Integrity
15 / 100

Data Integrity
normalization
16 / 100

Data Integrity
normalization
constraints (foreign keys, ...)
17 / 100

Data Integrity
normalization
Atomicity, Consistency, Isolation, Durability
18 / 100

Data Integrity
normalization
ACID compliant
19 / 100

Data Integrity
normalization
ACID compliant
transactions
20 / 100

Data Integrity
normalization
ACID compliant
transactions
SQL
21 / 100

Data Integrity
normalization
ACID compliant
transactions
SQL
powerfull query language
22 / 100

NoSQL & MySQL
NoSQL Databases
23 / 100

NoSQL or Document Store
Schemaless
24 / 100

Schemaless
no schema design, no normalization, no foreign keys, no data types, ...
25 / 100

Schemaless
very quick initial development
26 / 100

Schemaless
Flexible data structure
27 / 100

Schemaless
embedded arrays or objects
28 / 100

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

Schemaless
model
objects persistance without the use of any ORM - mapping oobject-oriented
30 / 100

Schemaless
model
JSON
31 / 100

Schemaless
model
JSON
close to frontend
32 / 100

Schemaless
model
JSON
close to frontend
native in JS
33 / 100

Schemaless
model
JSON
close to frontend
native in JS
easy to learn
34 / 100

How DBAs see data
35 / 100

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"
}
}
36 / 100

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 ?
37 / 100

DBMS or NoSQL ?
38 / 100

DBMS or NoSQL ?
Why not both ?
39 / 100

The MySQL Document Store !
SQL is now optional ?!
40 / 100

SQL is now optional ?!
41 / 100

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
42 / 100

MySQL Document Store
the Solution
43 / 100

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
44 / 100

X Protocol Connectors
45 / 100

X DevAPI We provide 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
46 / 100

PY
JS
SQL
>
MySQL 8.0
Upgrade Checker
Auto Completion
&
Command History
Output
Formats
(table, json, tabs)
Prompt
Themes
Batch
Execution
5.7
8.0
JS
Document
Store
X dev API
SQL CLI InnoDB
Cluster
importJSON
JSJS
47 / 100

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

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

50 / 100

51 / 100

Let´s query
52 / 100

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

54 / 100

Some more examples
55 / 100

Some more examples
Let´s add a selection criteria:
56 / 100

Using IN...
57 / 100

Syntax slightly different than MongoDB
58 / 100

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" }
59 / 100

And for developers ?
60 / 100

$session = mysql_xdevapigetSession("mysqlx://fred:MyP@ssw0rd%@localhost");
$schema = $session->getSchema("docstore");
$collection = $schema->getCollection("restaurants");
$results = $collection-> nd($search)->execute()->fetchAll();
...
foreach ($results as $doc) {
echo "<tr><td><a href='?id=${doc[_id]}'>${doc[name]}</a></td>";
echo "<td>${doc[borough]}</td><td>${doc[cuisine]}</td></tr>";
}
61 / 100

$session = mysql_xdevapigetSession("mysqlx://fred:MyP@ssw0rd%@localhost");
$schema = $session->getSchema("docstore");
$collection = $schema->getCollection("restaurants");
$results = $collection-> nd($search)->execute()->fetchAll();
...
foreach ($results as $doc) {
echo "<tr><td><a href='?id=${doc[_id]}'>${doc[name]}</a></td>";
echo "<td>${doc[borough]}</td><td>${doc[cuisine]}</td></tr>";
}

Easy, using only CRUD operations !
62 / 100

CRUD operations
63 / 100

CRUD operations for collections
Add a document
64 / 100

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()
65 / 100

Modify a document
66 / 100

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()
67 / 100

Remove a document
68 / 100

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

MySQL Document Store Objects Summary
70 / 100

All you need to know is here:
https://dev.mysql.com/doc/x-devapi-userguide/en/crud-operations-overview.html
71 / 100

we do care about your data
MySQL Document Store is Full ACID Compliant
72 / 100

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

innodb_ ush_log_at_trx_commit = 1
74 / 100

innodb_doublewrite = ON
75 / 100

sync_binlog = 1
76 / 100

sync_binlog = 1
transaction_isolation = REPEATABLE-READ|READ-
COMMITTED|...
77 / 100

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

MySQL DS Full ACID - Transactions support
79 / 100

MySQL DS Full ACID - Transactions support
80 / 100

OK we have Document Store, CRUD and ACID
but what makes MySQL Document Store unique ?
81 / 100

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
82 / 100

NoSQL as SQL - aggregation
83 / 100

84 / 100

85 / 100

NoSQL or SQL
You have the possibility to write clean and neat code:
86 / 100

NoSQL or SQL
$results = $collection-> nd('cuisine like "italian"')->execute()->fetchAll();
87 / 100

NoSQL or SQL
Or use SQL only when really needed:
88 / 100

NoSQL or SQL
$results = $session->sql('WITH cte1 AS (SELECT doc->>"$.name" AS name,
doc->>"$.cuisine" AS cuisine,
(SELECT AVG(score) FROM JSON_TABLE(doc, "$.grades[*]" COLUMNS (score INT
PATH "$.score")) AS r) AS avg_score FROM docstore.restaurants)
SELECT *, RANK()
OVER ( PARTITION BY cuisine ORDER BY avg_score) AS `rank`
FROM cte1 ORDER BY `rank`, avg_score DESC LIMIT 10;')->execute();
89 / 100

NoSQL or SQL
$results = $session->sql('WITH cte1 AS (SELECT doc->>"$.name" AS name,
doc->>"$.cuisine" AS cuisine,
(SELECT AVG(score) FROM JSON_TABLE(doc, "$.grades[*]" COLUMNS (score INT
PATH "$.score")) AS r) AS avg_score FROM docstore.restaurants)
SELECT *, RANK()
OVER ( PARTITION BY cuisine ORDER BY avg_score) AS `rank`
FROM cte1 ORDER BY `rank`, avg_score DESC LIMIT 10;')->execute();
All in the same MySQL X Session !
90 / 100

MySQL Shell is for DBAs and Developers

DEMO
91 / 100

what do I gain ?
Conclusion
92 / 100

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
93 / 100

95 / 100

http://lefred.be/content/top-10-reasons-for-
nosql-with-mysql/
96 / 100

97 / 100

May 9th, 2019
Hotel NH Collection Roma
Giustiniano
Via Virgilio, 1 E/F/G, 0019
ROMA
MySQL Day Roma
You are invited to listen last news on MySQL
8.0, watch demos and be in contact with the
MySQL Italian Team!
http://bit.ly/MySQLDayRoma2019
98 / 100

99 / 100

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

Oracle Code Roma: NoSQL + SQL = MySQL

Oracle Code Roma: NoSQL + SQL = MySQL

Recommended

More Related Content

What's hot

What's hot(20)

Similar to Oracle Code Roma: NoSQL + SQL = MySQL

Similar to Oracle Code Roma: NoSQL + SQL = MySQL(20)

More from Frederic Descamps

More from Frederic Descamps(20)

Recently uploaded

Recently uploaded(20)

Oracle Code Roma: NoSQL + SQL = MySQL