[{"data":1,"prerenderedAt":71},["ShallowReactive",2],{"term-p\u002Fpub-sub":3,"related-p\u002Fpub-sub":58},{"id":4,"title":5,"acronym":5,"body":6,"category":39,"description":40,"difficulty":41,"extension":42,"letter":15,"meta":43,"navigation":44,"path":45,"related":46,"seo":51,"sitemap":52,"stem":55,"subcategory":56,"__hash__":57},"terms\u002Fterms\u002Fp\u002Fpub-sub.md","Pub\u002FSub",{"type":7,"value":8,"toc":32},"minimark",[9,14,18,22,25,29],[10,11,13],"h2",{"id":12},"eli5-the-vibe-check","ELI5 — The Vibe Check",[15,16,17],"p",{},"Pub\u002FSub is like a newspaper service. Publishers write articles and drop them off. Subscribers sign up for topics they care about and get the relevant articles delivered. The publisher has no idea who's reading — they just keep publishing. No direct connections needed.",[10,19,21],{"id":20},"real-talk","Real Talk",[15,23,24],{},"Publish-Subscribe is a messaging pattern where publishers emit messages to named topics\u002Fchannels without knowing who will receive them. Subscribers register interest in specific topics and receive all matching messages. Decouples producers from consumers, enabling scalable asynchronous communication.",[10,26,28],{"id":27},"when-youll-hear-this","When You'll Hear This",[15,30,31],{},"\"We use Pub\u002FSub so the payment service doesn't need to know about the email service.\" \u002F \"Google Cloud Pub\u002FSub handles millions of events per second for us.\"",{"title":33,"searchDepth":34,"depth":34,"links":35},"",2,[36,37,38],{"id":12,"depth":34,"text":13},{"id":20,"depth":34,"text":21},{"id":27,"depth":34,"text":28},"architecture","Pub\u002FSub is like a newspaper service. Publishers write articles and drop them off.","intermediate","md",{},true,"\u002Fterms\u002Fp\u002Fpub-sub",[47,48,49,50],"Message Queue","Message Broker","Event-Driven Architecture","Observer Pattern",{"title":5,"description":40},{"changefreq":53,"priority":54},"weekly",0.7,"terms\u002Fp\u002Fpub-sub",null,"RYiAnxy5MGnoy7jBRnVg4xDOYiJsPfYcKEJUNbEKYPA",[59,62,65,68],{"title":49,"path":60,"acronym":56,"category":39,"difficulty":41,"description":61},"\u002Fterms\u002Fe\u002Fevent-driven-architecture","Event-Driven Architecture is like a gossip network. When something happens (order placed!), it broadcasts the news.",{"title":48,"path":63,"acronym":56,"category":39,"difficulty":41,"description":64},"\u002Fterms\u002Fm\u002Fmessage-broker","A Message Broker is the post office of your microservices world.",{"title":47,"path":66,"acronym":56,"category":39,"difficulty":41,"description":67},"\u002Fterms\u002Fm\u002Fmessage-queue","A Message Queue is a waiting room for tasks. Producers drop tasks in the queue, consumers pick them up and process them one at a time.",{"title":50,"path":69,"acronym":56,"category":39,"difficulty":41,"description":70},"\u002Fterms\u002Fo\u002Fobserver-pattern","Think of a newsletter. You (the publisher\u002Fsubject) publish content. Your subscribers (observers) automatically get notified when new content arrives.",1776518304485]