Ecto without SQL
summary
Ecto is presented as a toolkit, not just a DB layer: schemas as type definitions, changesets for validation and mapping, and adapters to back ends like ETS, MongoDB or key/value stores. Real use: validating incoming call-control commands at Telnyx by casting params into changesets, running validations, calling apply_changes to get a command struct, and passing that to a small controller—results: uniform error payloads, simpler controllers, easier tests. Notes the Ecto split into core ecto plus ecto_sql and that adapters can omit unsupported callbacks.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:16Context
- 5:56Ecto. Schema
- 13:39Ecto. Type . A behaviour for defining new Types
- 16:21Adapters
- 17:14Composing Things
- 19:11Repo without SQL
- 23:03Changesets without Repo
- 33:29What about the Ecto Split?
