This is the first in a series of posts about the MySQL JSON data type, how it compares to working with a document-oriented store like MongoDB, and how we can make use of it in the Laravel framework.
-
Part 1 is a quick look at the data type itself, and some of the functions available to work with that data. Specifically, we’ll focus on what kind of data to store and how to work with it, regardless of framework.
-
In Part 2 we’ll walk through which MongoDB patterns can be replicated in MySQL with the JSON type, as well as what can’t. We’ll also check out some alternative strategies for document-oriented storage using MySQL as a backing store.
-
Lastly, Part 3 will focus on using the JSON data type in Laravel applications, what contexts it is best suited for, and I’ll take a stab at some simple code you can use to …