Introducing The MySQL Document Store

Introducing
the
MySQL Document Store
Alfredo Kojima Sr. Dev. Manager
Mike Frank Product Management Director

Oracle
Copyright 2014 Oracle and/or its aliates. All rights reserved. | Oracle CondenNal Internal/Restricted/Highly Restricted
Safe Harbor Statement

The following is intended to outline our general product direcNon. It is intended for
informaNon purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or funcNonality, and should not be relied upon
in making purchasing decisions. The development, release, and Nming of any features or
funcNonality described for Oracles products remains at the sole discreNon of Oracle.
Copyright 2016 Oracle and/or its aliates. All rights reserved. |
Todays Agenda
1
RelaNonal Databases, Document Databases and MySQL
MySQL JSON Support
Document Use Cases
The X DevAPI
Ge\ng it all working together
RelaNonal Databases
Data Integrity
NormalizaNon
Constraints (foreign keys etc)
Atomicity, Consistency, IsolaNon, Durability - ACID

TransacNons
SQL
Powerful, OpNmizable Query Language
Declare what you want and the DB will nd out the most ecient way to get it to
you
Copyright 2016 Oracle and/or its aliates. All rights reserved. | Oracle CondenNal Restricted
Plus
MySQL has been around since 1995
Ubiquitous
Pregy much a standard
Scalable
When there are issues, they are known and understood
Large body of knowledge, from small to BIG deployments
Document Databases
Schemaless
no schema design, normalizaNon, foreign keys, constraints, data types etc
faster iniNal development
Flexible data structures

nested arrays and objects
some data is simply naturally unstructured or cannot be modeled eciently in the
relaNonal model (hierarchies, product DB etc)
persist objects without ORMs
Document Databases (Cont.)

JSON
Closer to the frontend
"naNve" in JavaScript
Node.js and full stack JavaScript
Easy to learn, easy to use
RelaNonal vs Document Databases

Why not both?
MySQL JSON Support
Document Use Cases
The X DevAPI
MySQL 5.7: JSON Support

NaNve JSON datatype
Store JSON values (objects, arrays and simple values) in MySQL tables
Binary JSON storage format
Conversion from "naNve" SQL types to and from JSON values
JSON ManipulaNon funcNons
Extract contents (JSON_EXTRACT, JSON_KEYS etc)
Inspect contents (JSON_CONTAINS etc)
Modify contents (JSON_SET, JSON_INSERT, JSON_REMOVE etc)
Create arrays and objects (JSON_ARRAY, JSON_OBJECT)
Search objects (JSON_SEARCH)
10
MySQL 5.7: JSON Support (cont.)

Inline SQL JSON path expressions
SELECT doc->'$.object.array[0].item' FROM some_table
Boolean operators (compare JSON values etc)

foo = doc->'$.eld'
11
MySQL 5.7: JSON Support (cont.)

Plus
Generated/Virtual Columns
Index JSON data
Foreign keys to JSON data
SQL views for JSON data
12
MySQL JSON Support
Document Use Cases
The X DevAPI

13
ExtracNng JSON from a RelaNonal DB

Rela+onal In, Rela+onal + Document Out
Data stored in relaNonal tables, but frontend uses JSON

JSON directly maps to naNve data structures in many languages
Oven easier for applicaNon code to use
JavaScript, Python, Ruby etc
In browser JavaScript
14
ExtracNng JSON from a RelaNonal DB

Rela+onal In, Rela+onal + Document Out
SQL FuncNons to construct JSON

JSON_OBJECT(), JSON_ARRAY()
Ex.:
SELECT JSON_OBJECT('cust_id', id, 'name', name, 'email', email) FROM customer;
CREATE VIEW customer_json AS
SELECT JSON_OBJECT('cust_id', id, 'name', name, 'email', email) as doc FROM
customer;
SELECT * FROM customer_json;
Updates and inserts sNll happen through the table columns

15
Using MySQL as a JSON Document Container

Document In, Rela+onal + Document Out
Virtually Schemaless
Unstructured data
No clear, xed structure for the data records can have dierent elds
Oven data that is not involved in business rules
Examples: "product_info", "properNes", "opNons" etc
Data does not map cleanly into a relaNonal model (arrays, hierarchical data
etc)
Prototyping
16
MySQL as a JSON Document Container

Example: "properNes" table
hgps://www.mediawiki.org/wiki/Manual:Database_layout
17

Example: "product_info" table
product_id a<ribute
value
size
color
red
fabric
cogon
11
avour
strawberry
12
capacity
128GB
12
speed class
class 10
13
connecNvity
Wi-Fi
13
storage
64GB
13
screen size
8.9"
13
resoluNon
2560 x 1600 (339 ppi)
13
bagery life
12 hours
{
"product_id": 9,
"size" : "M",
"color": "red",
"fabric": "cogon"
},
{
"product_id": 11,
"avour": "strawberry"
},
{
"product_id": 12,
"capacity": "128GB",
"speed class": "class 10"
},
{
18

Document In, Rela+onal + Document Out
An ordinary MySQL table with a single JSON data column

Generated columns allow SQL engine to look inside the JSON data
Virtual columns
Primary Keys
Indexes
Foreign Keys
Writes on the JSON column

Reads primarily from the JSON columns
19
Hybrid RelaNonal and JSON

Rela+onal + Document In, Rela+onal + Document Out
Database is mostly relaNonal

Some parts of the database are unstructured or does not model cleanly as
relaNonal
JSON columns in relaNonal tables
Queries can mix and match JSON and column data
EvoluNon path for Document based applicaNons
20
Hybrid RelaNonal and JSON

Rela+onal + Document In, Rela+onal + Document Out
product (product_id, name, category_id,
);
product (product_id, name, category_id,

, attributes JSON);
product_info (product_id, attribute,

value);
21
MySQL JSON Support
Document Use Cases
The X DevAPI

22
Document OperaNons via SQL

Powerful
Allows complex queries
But sNll dicult to use
23
Document OperaNons via SQL

CREATE TABLE product (
id VARCHAR(32) GENERATED ALWAYS AS (JSON_EXTRACT(doc, '$.id')) STORED,
doc JSON
);
INSERT INTO product VALUES (1, '{}');
SELECT * FROM product WHERE JSON_EXTRACT(doc, '$.field') = value;
etc.
24
The X DevAPI
AbstracNon over SQL
Focused on 4 basic CRUD operaNons (Create, Read, Update, Delete)
Fluent, NaNve Language API
No knowledge of SQL needed
X Protocol
CRUD requests encoded at protocol level
Request details "visible" (vs "opaque" SQL strings)
25
CollecNon and Schema OperaNons

Get a handle to a Schema
mydb = session.getSchema("mydb");

Create a CollecNon
mydb.createCollection("products");
Get a (local) reference to a CollecNon

products = mydb.getCollection("products");
26
Add Document
products.add({"name":"bananas", "color":"yellow"}).execute();
27
Find Documents
products.find("color = 'yellow'").sort(["name"]).execute();
28
Modify Documents
products.modify("product_id = 123").set("color", "red").execute();
29
Remove Documents
products.remove("product_id = 123").execute();
30
X DevAPI Sessions
X Session
Stateless
CRUD only, no SQL
Abstracts the connecNon
Node Session
Direct connecNon to a database node
Allows CRUD and SQL
31
Other OperaNons on CollecNons

Create an Index
db.post.createIndex("email").eld("author.email", "text(30)", false)
32
CRUD OperaNons NoSQL/Document and SQL/RelaNonal

Opera+on
Create
Read
Update
Delete
Document
CollecNon.add()
CollecNon.nd()
CollecNon.modify()
CollecNon.remove()
Rela+onal
Table.insert()
Table.select()
Table.update()
Table.delete()
33
MySQL JSON Support
Document Use Cases
The X DevAPI

34
5.7.12 Development Preview Release

MySQL 5.7.12 with Document Store plugin
MySQL Shell 1.0.3
Connector/J 7.0
Connector/Net 7.0
Connector/Node.js 1.0
35
MySQL 5.7, Connectors, Drivers, and Protocols

MySQL Connectors and Drivers
SQL API
CRUD and SQL APIs
Std Protocol
X Protocol
X and Std
Protocols
X Protocol
33060
Std Protocol
3306
MySQL
Shell
Memcached
driver
Memcache
Protocol
MySQL
Plugins
Core
X Protocol Plugin
Memcached Plugin
36
X DevAPI Connectors MySQL Connector/Java 7.0

uri = "mysql:x://localhost:33060/test?user=user&password=mypwd"';!
DbDoc book = docs.fetchOne();!
XSession session = new MysqlxSessionFactory().getSession(uri);!
System.err.println("Currently reading "!

+ ((JsonString)book.get("title")).getString() !
+ " on page " !
+ ((JsonNumber)book.get("currentlyReadingPage")).getInteger());!
Schema schema = session.getDefaultSchema();!

// document walkthrough!
Collection coll = schema.createCollection("myBooks", true);!
DbDoc newDoc = new DbDoc().add("isbn", !
new JsonString().setValue("12345"));!
!
// increment the page number and fetch it again!
newDoc.add("title", !
new JsonString().setValue("Effi Briest"));!
coll.modify("isbn = 12345").!
set("currentlyReadingPage", !
((JsonNumber)book.get("currentlyReadingPage")).getInteger() +
1).execute();!
newDoc.add("author", !
new JsonString().setValue("Theodor Fontane"));!
docs = coll.find("title = 'Effi Briest' and currentlyReadingPage >

10").execute();!
newDoc.add("currentlyReadingPage", !
new JsonNumber().setValue(String.valueOf(42)));!
book = docs.fetchOne();!
coll.add(newDoc).execute();!
DocResult docs = coll.find("title = 'Effi Briest' and
currentlyReadingPage > 10").execute();!
System.err.println("Currently reading " !

+ ((JsonString)book.get("title")).getString() !
+ " on page "!
+ ((JsonNumber)book.get("currentlyReadingPage")).getInteger());!
37
X DevAPI Connectors MySQL Connector/Net 7.0

using (XSession session =
Result r = coll.Add(docs).Execute();
MySQLX.GetSession("mysqlx://test:test@localhost:33060")) Console.WriteLine("Docs added: " + r.RecordsAffected);

{
string schemaName = "test";
// modify some values
Schema testSchema = session.GetSchema(schemaName);
r = coll.Modify("_id = :ID").
if (testSchema.ExistsInDatabase())
Bind("Id", 2).Set("pages", "25").Execute();
session.DropSchema(schemaName);
Console.WriteLine("Docs modified: " + r.RecordsAffected);
session.CreateSchema(schemaName);
// remove a book
// insert some docs
r = coll.Remove("_id = :ID").Bind("Id", 4).Execute();
Collection coll = testSchema.CreateCollection("myDocs");
Console.WriteLine("Docs removed: " + r.RecordsAffected);
var docs = new[]
// list the results
new { _id = 1, title = "Book 1", pages = 20 },
var result30orMore = coll.Find("pages > 20").
OrderBy("pages DESC").Execute().FetchAll();
foreach(var doc in result30orMore)
};
Console.WriteLine(doc.ToString());
}
}

38
X DevAPI Connectors MySQL Connector/Node.js 1.0 NEW!

const mysqlx = require('mysqlx');!
const collection =
session.getSchema('myschema').getCollection('questions');!
mysqlx.getSession({!
collection.find("answer == 42")!
host: 'localhost',!
.orderBy("foo DESC")!
dbUser: 'myuser',!
.limit(10)!
dbPassword: 'secret'!
}).then(session => {!
const collection =
session.getSchema('myschema').getCollection('mycollection');!
return Promise.all([!
collection.add({ foo: "bar", something: { nested:
[1,2,3,4] } }).execute();!
session.close();!
.execute(doc => console.log(doc)) // print the document

received, callback called for each doc!
.then(() => console.log("All done") // Promise resolves
when all data is there!
.catch((err) => console.log("Oups, an error", err);!
!

])!
}).catch(err => {!
console.log(err);!
});!
!
39
MySQL Shell
40
MySQL Plugin for VisualStudio
41
Resources
Topic
Link(s)
MySQL as a Document Database
hgp://dev.mysql.com/doc/refman/5.7/en/document-database.html

MySQL Shell
hgp://dev.mysql.com/doc/refman/5.7/en/mysql-shell.html
hgp://dev.mysql.com/doc/refman/5.7/en/mysqlx-shell-tutorial-javascript.html
hgp://dev.mysql.com/doc/refman/5.7/en/mysqlx-shell-tutorial-python.html
X Dev API
hgp://dev.mysql.com/doc/x-devapi-userguide/en/
X Plugin
hgp://dev.mysql.com/doc/refman/5.7/en/x-plugin.html
MySQL JSON
hgp://mysqlserverteam.com/tag/json/
hgps://dev.mysql.com/doc/refman/5.7/en/json.html
hgps://dev.mysql.com/doc/refman/5.7/en/json-funcNons.html
Blogs
hgp://mysqlserverteam.com/category/docstore/
42
Thank You!
Alfredo Kojima
alfredo.kengi.kojima@oracle.com

Introducing The MySQL Document Store

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Introducing The MySQL Document Store

Încărcat de

Drepturi de autor:

Formate disponibile

Introducing

Safe Harbor Statement

Copyright 2016 Oracle and/or its aliates. All rights reserved. |

RelaNonal Databases, Document Databases and MySQL

MySQL JSON Support

Document Use Cases

Ge\ng it all working together

Copyright 2016 Oracle and/or its aliates. All rights reserved. |

Atomicity, Consistency, IsolaNon, Durability - ACID

Flexible data structures

Document Databases (Cont.)

Easy to learn, easy to use

RelaNonal vs Document Databases

RelaNonal Databases, Document Databases and MySQL

MySQL JSON Support

Document Use Cases

Ge\ng it all working together

Copyright 2016 Oracle and/or its aliates. All rights reserved. |

MySQL 5.7: JSON Support

MySQL 5.7: JSON Support (cont.)

SELECT doc->'$.object.array[0].item' FROM some_table

Boolean operators (compare JSON values etc)

MySQL 5.7: JSON Support (cont.)

RelaNonal Databases, Document Databases and MySQL

MySQL JSON Support

Document Use Cases

Ge\ng it all working together

ExtracNng JSON from a RelaNonal DB

Data stored in relaNonal tables, but frontend uses JSON

ExtracNng JSON from a RelaNonal DB

SQL FuncNons to construct JSON

Updates and inserts sNll happen through the table columns

Using MySQL as a JSON Document Container

MySQL as a JSON Document Container

MySQL as a JSON Document Container

2560 x 1600 (339 ppi)

MySQL as a JSON Document Container

An ordinary MySQL table with a single JSON data column

Writes on the JSON column

Hybrid RelaNonal and JSON

Database is mostly relaNonal

Hybrid RelaNonal and JSON

product (product_id, name, category_id,

product_info (product_id, attribute,

RelaNonal Databases, Document Databases and MySQL

MySQL JSON Support

Document Use Cases

Ge\ng it all working together

Document OperaNons via SQL

Document OperaNons via SQL

CollecNon and Schema OperaNons

Get a (local) reference to a CollecNon

products.modify("product_id = 123").set("color", "red").execute();

Other OperaNons on CollecNons

CRUD OperaNons NoSQL/Document and SQL/RelaNonal

Copyright 2016 Oracle and/or its aliates. All rights reserved. |

RelaNonal Databases, Document Databases and MySQL

MySQL JSON Support

Document Use Cases

Ge\ng it all working together

5.7.12 Development Preview Release

MySQL 5.7, Connectors, Drivers, and Protocols

CRUD and SQL APIs