Get Your CRUD Together!

on YouTube ↗41m

" summary

Argues CRUD apps for small teams benefit from a dedicated data access layer that wraps Ecto into a GenericRepo macro, uses composable Ecto queries and clear Boundaries to standardize shapes and reduce variation. Demonstrates code: repo.all/get/create/update wrappers, named bindings for joins, and returning {:ok, value} or {:error, reason} instead of nil. Targets internal apps with ~hundreds of users, claims faster time to market and fewer bugs, and warns the pattern works well from 0→1 but can be outgrown as traffic and complexity rise.

AI-written summary · about

" chapters (6)

1. 0:0005:45 - Intro
2. 5:4610:02 - Motivations
3. 10:0315:22 - The Data Access Layer
4. 15:2318:50 - Patterns I Like
5. 18:5125:16 - Compasable Queries
6. 25:1740:57 - The GenericRepo

" related talks

• 50mMoving away from CRUD: DDD + CQRSForat Latif · Codemotion Roma 2014
• 41mAPPLICATION ARCHITECTURE: BOUNDARIES, OBJECT ROLES, & PATTERNSAdam Hawkins · wroc_love.rb 2014
• 24mThe Alchemist's Code: Bringing More Value with Less MagicRafał Studnicki · Code Elixir LDN 2019
• 41mFrom CRUD to DDD: how did we end up here?Arnout Boks · Dutch PHP Conference 2024
• 43mThe Clean Architecture: How to Grow From Startup to EnterpriseVolodymyr Vorobiov · RubyC 2018
• 19mStructs for orderAndrey Chernykh · Code BEAM Lite Berlin 2018
• 44mHow Do You Structure Your Go Apps?Kat Zień · GopherCon Europe - Iceland 2018
• 47mElixir for curing product development painsMichael Krax · Code Elixir LDN 2018