Should we use a JSON field for this? - Listen - No Compromises

Should we use a JSON field for this?

Listen now

Description

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

See all »

Taking liberties with value objects

Programmers love geeking out and creating specialized terms and vocabulary. Well I can do that too. In today's episode, we talk about "value objects", put our own special definition on it, and discuss when we might use these in a Laravel project. (00:00) - What I mean by "value object" (03:00)...

Published 11/23/24

No Compromises

Published 11/23/24

How to deal with things outside your control on a dev project

Have you ever struggled working with a third party on one of your developer projects? How do you handle that, keeping it professional and also still able to meet your commitments? In today's episode of No Compromises, Aaron and Joel discuss what happened on a recent project and how they think...

Published 11/09/24