JSON fields can be very useful, but when is a good time to include them in your database design?
In today's episode of No Compromises, Aaron and Joel use a couple examples from recent projects to talk through reasons they would and would not use a JSON field.
- (00:00) - Debating JSON fields in database design
- (03:06) - Configuration options: JSON vs. relational tables
- (07:05) - Real-world example: label customization dilemma
- (11:30) - Silly bit
Want a place to ask any question related to Laravel development? Check out the
Mastering Laravel community.
