Using Ecto.Multi to Keep Database Operations Atomic in Elixir
Group several Ecto changesets into a single transaction with Ecto.Multi, ensuring all succeed or none happen, while avoiding nested manual rollbacks.
Loading…
ReadMeFeed / Community knowledge
Phoenix
Real questions. Useful conversations. Find the people who know your stack.
Phoenix
Frameworks & web · #phoenix
Phoenix Secondary Indexes vs Row-Key Range Scans
Choose between Phoenix secondary indexes and row-key range scans, then validate with EXPLAIN before and after index creation.
Using Apache Phoenix Secondary Indexes Without Slowing Writes
Speed up non-row-key lookups in Apache Phoenix with secondary indexes, but verify planner selection with EXPLAIN and account for write amplification.
Managing Large Lists in Phoenix LiveView with Streams
Learn how to use Phoenix LiveView Streams to handle large data collections without exhausting server memory or slowing down WebSocket updates.
Reducing Client-Side State with Phoenix LiveView
Stop duplicating state between your API and frontend. Learn how Phoenix LiveView uses server-side processes and WebSockets to handle real-time UI with minimal JavaScript.
Apache Phoenix Materialized Views: When to Pre-Aggregate HBase Data
Decide whether a Phoenix materialized view fits your HBase aggregation workload, with option trade-offs, sample DDL, and validation checks.
Using Phoenix Secondary Indexes to Speed Non-Key Queries on HBase
Filtering a Phoenix table by a non‑key column forces a full table scan. Adding a secondary index turns that scan into an index lookup, cutting read latency while adding modest write overhead.
Selecting Secondary Index Types in Apache Phoenix: Global vs. Local
Compare Global and Local secondary indexes in Apache Phoenix to balance write throughput and read latency in HBase-backed applications.
Phoenix Secondary Indexes: Choosing Global vs. Local Without Doubling Your Writes
Phoenix secondary indexes are separate HBase tables, not magic. Learn when a global index is worth the synchronous write cost, when a local index fits your access pattern, and how covering columns trade storage for read speed.