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.
Loading…
ReadMeFeed / Community knowledge
#phoenix-framework
Real questions. Useful conversations. Find the people who know your stack.
Managing Real-Time State with Phoenix Channels and Presence
Learn how to use Phoenix Channels and the Presence module to manage real‑time user state across distributed clusters without relying on a central database.
Managing State Synchronization in Phoenix Channels with PubSub
Learn how to synchronize state across distributed Phoenix nodes using PubSub to build scalable, real-time bidirectional communication.
Phoenix LiveView vs REST API for Real-Time Dashboards: A Decision Guide
Decision guide for building a real-time Phoenix dashboard: compare LiveView server rendered versus REST API plus SPA, with trade-offs, constraints, and a concrete LiveView sketch for validation.
phoenixWhen Phoenix LiveView Replaces Your JavaScript Framework — and When It Shouldn't
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.
Reducing Frontend Complexity with Phoenix LiveView State Management
Stop building redundant APIs. Learn how Phoenix LiveView moves state management to the server to reduce frontend complexity and enable real-time updates via diff-based HTML patches.
Can Phoenix Channels avoid mailbox buildup during concurrent broadcasts?
Phoenix Channels rely on the BEAM VM's lightweight process model and a pub-sub mechanism to deliver messages to connected clients asynchronously. Presence tracks user state across a distributed cluster without a central bottleneck, and each client connection is isolated in its own process under actor-model semantics. The design goal is to understand latency