Listen "Should we use a JSON field for this?"
Episode Synopsis
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.
More episodes of the podcast No Compromises
Why I changed my mind about down migrations
03/01/2026
Why senior developers feel wrong more often
20/12/2025
Should you ever hand-format code?
06/12/2025
Discussing different ways to model data
22/11/2025
Read outside tech to expand your horizons
08/11/2025
Should you use DTOs in Laravel?
27/09/2025
Sunsetting a company app without loose ends
13/09/2025
ZARZA We are Zarza, the prestigious firm behind major projects in information technology.