Should you use DTOs in Laravel?

No Compromises

Content provided by Joel Clermont and Aaron Saray. All podcast content including episodes, graphics, and podcast descriptions are uploaded and provided directly by Joel Clermont and Aaron Saray or their podcast platform partner. If you believe someone is using your copyrighted work without your permission, you can follow the process outlined here https://podcastplayer.com/legal.

23d ago 10:10

MP3•Episode home

DTOs (Data Transfer Objects) aren't mentioned anywhere in the Laravel docs, but some devs use them heavily in their applications, whereas other devs never use them at all.

In the latest episode of the No Compromises podcast, we weigh the pros and cons of DTOs in everyday Laravel apps, comparing them to form requests, PHPDoc-typed arrays, and service-layer boundaries, and share one area where DTOs truly shine.

The takeaway: keep DTOs in the toolbox, but reach for them intentionally, not by habit.

(00:00) - Framing DTOs in a stricter PHP world
(01:15) - Our current practice: hybrids, few true DTOs
(02:45) - Form requests, `safe()`, and typed inputs
(03:45) - Reuse across API and form layers rarely aligns
(04:30) - Where DTOs shine: normalizing multiple APIs
(05:45) - Service boundaries: wrapping vendor objects (e.g., Stripe)
(06:15) - PHPDoc-typed arrays vs DTO overhead
(06:45) - Conventions, Larastan levels, and avoiding ceremony
(07:45) - Treat DTOs as a tool, not a rule
(09:15) - Silly bit

Want to discuss how we can help you with an architecture review?

137 episodes

#Tech #Joel Clermont #Aaron Saray