Ecto.Schema without Ecto.Repo
summary
Claims that Ecto.Schema without Ecto.Repo works as a standalone data layer for microservices, using embedded_schema and cast_embed to parse JSON and RabbitMQ payloads, and custom types and validators to coerce legacy integers and enforce rules. A tiny JSON API that creates pet objects demonstrates apply_changes for valid data and error extraction for nested embeds. Limitations: no hook for custom-type error messages, no built‑in uniqueness/primary‑key checks without a DB, and awkward input/output field remapping.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:30About RentPath
- 1:02EctoSchema
- 2:06Demo
- 2:40Error Response
- 3:13Embedded Schema
- 4:00Embeds
- 4:45Inline Style
- 5:27Custom Type
- 6:24Error Messages
- 7:48validators
- 8:20apply changes
- 9:16recursive logic
- 9:50Limitations
- 14:56Outro
related talks
35mUsing Semantic Metadata to Create an Automated Microservice Data Mesh
19mValidating Event Driven Architecture (EDA) with AsyncAPI
45mMicro Services and Events: Friends or Foes?
46mState or events? Which shall I keep?
37mGraphQL and Microservices or How we learned to be big and small at the same time
39mEvent Sourcing made Simple
15mMicroservices with Elixir
27mWhy GraphQL is Perfect For Microservices