You don't need NoSQL (use MySQL)

MySQL has first party support for JSON documents and it can be a really nice escape hatch from the rigid structure of a relational database.

To learn more, check out some videos from our free course:

Or some of our blog posts:

---------------
00:00 MySQL supports NoSQL
01:15 When to use JSON
04:20 JSON versus TEXT columns
07:00 Efficient JSON storage
07:45 Creating JSON objects with SQL
11:00 Extracting JSON from the document
14:40 JSON arrays
17:20 Querying on JSON columns
18:50 Query an array's items
19:40 Indexing JSON documents
22:48 Generated columns
26:00 JSON blob storage
27:09 Making JSON invisible
29:00 Updating documents in place
---------------

💬 Follow PlanetScale on social media

[rdvansloten]

This channel pumps out quality database content every week. Definitely deserves more subscribers.

[LenWoodward]

I'm absolutely loving this long-form content, Aaron. So easy to just put each one of these in my `favorites` list. So much value.

[xcrap]

I have never used, and probably will not, but I have to admit, that's incredibly powerful. Super educational information as usual. I think the only thing missing in some videos would be some real-case measurements and testing. For example, there could be two tables: one with JSON elements and another without. We could compare the speed of SELECTs from a million table data. I think this will not only be useful but also very informative about what kind of tables or schemas are more suitable for specific case scenarios. For example It could help us make informed decisions when creating product items attributes in a shop, whether it's better to use JSON or just columns.

MYSQL is really powerful ;)

[antonmykhailovskyi]

I don`t really often leave comments but you deserved it)) Ngl, I`ve never seen neither more useful, nor "pleasant-to-listen" tutorials in MySQL topic. The way you, Aaron, explain things to us is out of this world, do love it!
Keep it up, I`m completely sure many people will find it useful!

[nathanbrown]

Three minutes into watching this, and I'm already loving the wonderful variety of use cases you have come up with! Feels like a NoSQL approach within a relational db

[MatthiasFeist-de]

those videos you make are really great. I worked with mySQL since 15 years ago but I still learn something new and really enjoy the format and your delivery of these topics!

[xjrr]

This series of videos are incredible, been watching all of them and it really helps me out. Thanks for your work, keep it going.

[MrOptima]

Excellent video and resource link to Digital Ocean. I was living in dark ages using MySQL version 5.2x. I upgraded to 8.0.35 and experimented with everything you mentioned in the video. It opened my eyes on how to use MySQL with JSON moving forward. I was using a text field for that before and did not know about all the JSON related functions of MySQL. Thank you very much.

I did exactly that in a postgresql db. This is fantastic, much more solid and fast

[kyleareich]

Dude you're one of the best teachers I've ever run across on the internet or in person. Thanks for what you do. I love your videos.

[Cookie-mvhg]

I love your courses and the way you explain about things. Please keep doing it!

[Tigerlady]

I just stumbled across this video and I haven't finished it but I already love it!

I'm still learning about databases but I thought NoSQL was hands down more powerful and scalable than SQL tables, and my previous experience with SQL tables has been a drag, but this is showing me a side of SQL tables I didn't know existed. Thanks!

[kilian]

I really enjoyed this tutorial. I'm new to DBs as a whole, getting this insight into how JSON-Documents can be handled independently of a NoSQL-DB will surely be useful. I will hopefully be doing a project for changelog-storage in the near future, where this might come in handy!

[Sabach]

We often have an "options_json" column where we set configurations of things that we don't directly search often. An example would be on our forms builder, the forms settings someone picks we use to generate the form, or even on questions if a certain question type is required or has visibility requirements, etc. It saves scanning a ton of extra columns.

[BudaSuyasa]

Wow, i been using MySQL all of my career and this video blown my mind. So much value as always Aaron.

[ANIALLATOR]

Awesome video content as always! Love seeing a video from this channel pop up in my feed ❤

[arielspalter]

Excellent tutorial. Eloquently and clearly explained and demonstrated.

[rasalas]

I saw the field type a few months ago and it blew my mind.

It felt like everything NoSQL was "known good for" just "vanished".
I can just keep using MySQL for most of my stuff :D

I still didn't know about some of the things you showed, so thanks <3

[Boubiboom]

This is so good, you do an amazing job !! It’s crystal clear, we learn a lot, thank you very much ! 👍

[timucinbahsi]

I'd like to add to this. Some of the reasons for using NoSql are being able to store the data in RAM like using Redis for cache etc and also NoSql is scalable. Both of those also possible in Sql databases. You can definitely configure your db to be stored in the memory and you can definitely have a cluster of Sql database. It is harder to scale up relationships with both Sql and NoSql. NoSql just defaults to having no relationships what so ever. That's what makes it easier to scale. If you do introduce relationships in your data, you'll have the same issues. Needless to say Sql databases are perfectly capable of not using relationships