ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #elixir
Ecto.Multi models database transactions as explicit, composable data structures instead of callback blocks. This post walks through a registration pipeline, shows how steps share results via an accumulator, and explains why keeping side effects out of the transaction matters.
An architecture note on keyset (cursor) pagination in Ecto: when it beats OFFSET, the smallest working design, cursor trust boundaries, and the failure modes to test for.
Explains how to use Elixir GenServers for safe state management, covering requirements, minimal design, process boundaries, supervision, monitoring, and when to adjust the architecture.
Learn how to mount a LiveView, handle state, and prepare for high‑traffic production with Phoenix 1.7+. The guide covers prerequisites, a step‑by‑step setup, debugging tips, and recovery strategies.
Learn how to architect Phoenix Channels for real‑time apps: isolate state, enforce data boundaries, monitor PubSub, and handle failures. Includes a concrete persistent chat example and guidelines for scaling.
Stop using fat models for validation. Learn how Ecto Changesets decouple data transformation from persistence to prevent mass-assignment vulnerabilities and handle race conditions.
Phoenix LiveView can delete your duplicated validation and state layer — for the right features. A worked form example, its test, and the line where LiveView stops fitting.
An architecture note on Ecto.Multi: when atomic multi-step writes justify it, the minimal pipeline design, trust boundaries, operational checks, and when to switch to sagas or chunked transactions.
Phoenix LiveView lets Ecto changesets power real-time form validation over a WebSocket — no client-side JavaScript. A worked registration form example, plus latency and state trade-offs.
ecto
phoenix