Article: Real-time updates without a message broker

Most real-time tutorials reach for Redis or a dedicated broker before writing a single line of feature code. For a lot of apps that is premature: a single long-lived WebSocket process can fan out events just fine.

Phlo bundles its realtime layer into the same daemon that serves HTTP, so a published article can push a notification to connected editors with no extra infrastructure. State stays in one place and deploys stay boring.

You can always graduate to a broker once you genuinely outgrow one node. Until then, fewer moving parts means fewer 3am pages.