Discussing different ways to model data

It's easy to overcomplicate data modeling, especially when enums, relationships, and future requirements are in play.

In the latest episode of the No Compromises podcast, Joel brings Aaron a real-world technical dilemma: how to model a relationship between two models when types are stored as enums, not models.

We discuss the pros and cons of pivot tables versus JSON columns, the importance of context before jumping to solutions, and how developer instincts can sometimes get in the way of clarity.

(00:00) - Setting up the technical problem
(02:00) - Pivot tables vs JSON columns
(05:15) - Filtering and validation considerations
(07:15) - Deciding on the best approach
(09:50) - Silly bit

Would you like us to review your code or application architecture?

Discussing different ways to model data

About this Episode

Hosts & Guests

More from No Compromises

Do you actually own the code you ship?

Do you actually need a multi-tenancy package?

Local and production should match even for Laravel tools

When weird code needs to explain itself