Using Redis Pub/Sub for Fire-and-Forget Messaging: Setup, Limits, and Checks
Learn how Redis Pub/Sub implements fire‑and‑forget messaging, see a two‑terminal setup, and discover limits like message loss, buffer bloat, and cluster overhead.
Loading…
ReadMeFeed / Community knowledge
#pubsub
Real questions. Useful conversations. Find the people who know your stack.
redisUsing Google Cloud Pub/Sub Push Subscriptions with OIDC for Secure Webhook Delivery
Learn how to configure Google Cloud Pub/Sub push subscriptions with OIDC tokens so that external webhooks receive authenticated events without managing custom token services.
googlePhoenix Channels PubSub: Memory Overhead vs Broadcast Latency in High-Concurrency Clusters
Scaling State Distribution Phoenix Channels rely on a pub-sub mechanism to synchronize state across a cluster. While the BEAM handles concurrent TCP connections efficiently via Cowboy, the memory overhead associated with maintaining active process states increases as the number of concurrent subscribers grows. When scaling to thousands of concurrent users, t
phoenixWaku topic filter subscriptions stop matching after upgrading past v0.24
Symptom After upgrading Waku nodes from a pre-v0.24 release, subscriptions that previously matched published messages no longer deliver them, even though the topic names and publisher code are unchanged. The goal is to restore selective delivery on topic-based pub/sub without falling back to receiving every message on the Gossipsub subgraph. Context and cons
wakuPub/Sub emulator bypassing IAM enforcement during local testing
The Google Cloud Pub/Sub emulator allows for local development by setting the PUBSUB_EMULATOR_HOST environment variable. However, when active, the emulator bypasses standard OAuth 2.0 token validation and IAM permission checks. This current permissive behavior creates a discrepancy between local testing environments and production. While the emulator accepts
Phoenix.PubSub adapter selection for low-traffic cost optimization
Infrastructure Cost vs. Scalability \n When deploying a low-traffic Phoenix application, minimizing operational overhead and monthly spend is a primary goal. The choice of Phoenix.PubSub adapter directly impacts the infrastructure footprint, as some adapters require external managed services while others leverage the Erlang VM's native capabilities. \n Adapt
elixirError: 7 PERMISSION_DENIED: User not authorized to perform this action when publishing to Pub/Sub from Cloud Function
Goal Determine how to validate Pub/Sub publish permissions for a Cloud Function before deployment so that the function works both in the local emulator and in production without encountering a PERMISSION_DENIED error. Constraints and Uncertainty The Cloud Functions emulator with --allow-local bypasses IAM checks, allowing the function to use the local user’s
Silent message loss in Phoenix.PubSub when scaling to a second non‑clustered node
Goal: Determine the safest, lowest‑cost approach to handle Phoenix.PubSub when a low‑traffic application might later be scaled to a second node. Constraints: The current cheapest setup runs a single release with server mode enabled, relies on the default PG2‑style PubSub adapter, and accepts a brief availability gap during each deploy. Adding a second node w