[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"glossary-publish-subscribe::en":3,"gloss-cluster-publish-subscribe::en":23,"gloss-next-publish-subscribe::en":9},{"slug":4,"category":5,"name":6,"definition":7,"meta_desc":8,"faq":9,"schema_markup":9,"related":10},"publish-subscribe","integration","Publish\u002FSubscribe (Pub\u002FSub)","Publish\u002Fsubscribe (pub\u002Fsub) is a messaging pattern where senders — publishers — emit events to a named channel or topic without knowing or caring who receives them, and any number of interested consumers — subscribers — independently receive a copy. A message broker sits in the middle, decoupling the two sides completely: the publisher just announces \"an order was placed,\" and whichever services care (billing, email, analytics, inventory) each react on their own. This differs from a point-to-point queue, where each message is handled by exactly one worker; with pub\u002Fsub, one event fans out to many. For SaaS builders, pub\u002Fsub is the backbone of event-driven architecture. It lets you add new functionality — a Slack notification, a data-warehouse sync — by subscribing a new consumer to existing events, without touching the code that publishes them. That loose coupling is what keeps a growing system maintainable. The trade-offs to plan for: messages can arrive more than once (so consumers should be idempotent) and delivery is asynchronous, so downstream effects aren't instant.","Publish\u002Fsubscribe lets publishers emit events to a topic without knowing who listens, while any number of subscribers each get a copy through a broker in the middle.",null,[11,14,17,20],{"slug":12,"name":13},"dead-letter-queue","Dead-Letter Queue (DLQ)",{"slug":15,"name":16},"message-queue","Message Queue",{"slug":18,"name":19},"server-sent-events","Server-Sent Events (SSE)",{"slug":21,"name":22},"webhook","Webhook",[24,28,31,34,37,40,44,47,50,53,56,59],{"slug":25,"category":5,"name":26,"updated_at":27},"backend-for-frontend","Backend for Frontend (BFF)","2026-08-24T02:46:38+00:00",{"slug":29,"category":5,"name":30,"updated_at":27},"concurrency-limit","Concurrency Limit",{"slug":32,"category":5,"name":33,"updated_at":27},"event-ordering","Event Ordering",{"slug":35,"category":5,"name":36,"updated_at":27},"field-mapping","Field Mapping",{"slug":38,"category":5,"name":39,"updated_at":27},"function-schema","Function Schema",{"slug":41,"category":5,"name":42,"updated_at":43},"grpc","gRPC","2026-08-24T02:46:37+00:00",{"slug":45,"category":5,"name":46,"updated_at":27},"integration-marketplace","Integration Marketplace",{"slug":48,"category":5,"name":49,"updated_at":27},"ip-allowlist","IP Allowlist",{"slug":51,"category":5,"name":52,"updated_at":27},"json-web-token","JSON Web Token (JWT)",{"slug":54,"category":5,"name":55,"updated_at":27},"mcp-server","MCP Server",{"slug":57,"category":5,"name":58,"updated_at":27},"mutual-tls","Mutual TLS (mTLS)",{"slug":60,"category":5,"name":61,"updated_at":27},"oauth-scopes","OAuth Scopes"]