[{"data":1,"prerenderedAt":81},["ShallowReactive",2],{"term-e\u002Fevent-driven-architecture":3,"related-e\u002Fevent-driven-architecture":61},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":55,"sitemap":56,"stem":59,"subcategory":6,"__hash__":60},"terms\u002Fterms\u002Fe\u002Fevent-driven-architecture.md","Event-Driven Architecture",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"Event-Driven Architecture is like a gossip network. When something happens (order placed!), it broadcasts the news. Anyone who cares (inventory service, email service, analytics) picks it up and reacts. Services don't call each other directly — they just react to events.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Event-Driven Architecture is a software design paradigm where components communicate by producing and consuming events. Decouples producers from consumers, enables asynchronous processing, and improves scalability. Core components: event producers, event channels (queues\u002Ftopics), and event consumers.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"We use event-driven architecture so services don't need to know about each other.\" \u002F \"The order service publishes an event; the warehouse service handles fulfillment independently.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"architecture","Event-Driven Architecture is like a gossip network. When something happens (order placed!), it broadcasts the news.","intermediate","md","e",{},true,"\u002Fterms\u002Fe\u002Fevent-driven-architecture",[49,50,51,52,53,54],"Pub\u002FSub","Message Queue","CQRS","Event Sourcing","Observer Pattern","Message Broker",{"title":5,"description":41},{"changefreq":57,"priority":58},"weekly",0.7,"terms\u002Fe\u002Fevent-driven-architecture","fwDSf8eevLMnhZ9bc3TzyxXRyyc1PjFV7BDedFU_cMk",[62,66,69,72,75,78],{"title":51,"path":63,"acronym":6,"category":40,"difficulty":64,"description":65},"\u002Fterms\u002Fc\u002Fcqrs","advanced","CQRS says: the way you write data and the way you read data should be separate systems. Writing (commands) goes to one model optimized for transactions.",{"title":52,"path":67,"acronym":6,"category":40,"difficulty":64,"description":68},"\u002Fterms\u002Fe\u002Fevent-sourcing","Instead of storing 'balance: $100', event sourcing stores 'deposited $200, withdrew $50, withdrew $50'.",{"title":54,"path":70,"acronym":6,"category":40,"difficulty":42,"description":71},"\u002Fterms\u002Fm\u002Fmessage-broker","A Message Broker is the post office of your microservices world.",{"title":50,"path":73,"acronym":6,"category":40,"difficulty":42,"description":74},"\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":53,"path":76,"acronym":6,"category":40,"difficulty":42,"description":77},"\u002Fterms\u002Fo\u002Fobserver-pattern","Think of a newsletter. You (the publisher\u002Fsubject) publish content. Your subscribers (observers) automatically get notified when new content arrives.",{"title":49,"path":79,"acronym":49,"category":40,"difficulty":42,"description":80},"\u002Fterms\u002Fp\u002Fpub-sub","Pub\u002FSub is like a newspaper service. Publishers write articles and drop them off.",1776518278016]