#Pubsub
5 notas · última:
Distributed PubSub in Elixir
The article builds a local PubSub with Registry, then extends it to a clustered setup with pg and libcluster so each node relays messages to local subscribers.
Building a Real-time Kanban Board with Phoenix LiveView
The post walks through building a minimal Kanban board with Phoenix LiveView, from project setup and Ecto schemas to LiveView events, PubSub broadcasts, and drag-and-drop updates.
Communicating between LiveViews on the same page
The post compares ways for multiple LiveViews on one page to communicate: via parent and child PIDs, sibling routing through a shared ancestor, or PubSub scoped by root PID or page ID.
Guts of Phoenix websocket channels
The post breaks Phoenix channels into transport, channel, and PubSub layers, then explains how Cowboy, GenServers, ETS, and PG2 move messages between clients and nodes.
How to work with multiple Channels in Phoenix?
The thread asks whether user info can be shared across Phoenix topics through the socket struct. Chris McCord says the client must join each topic, while socket params and channel params can carry shared data.