[{"data":1,"prerenderedAt":74},["ShallowReactive",2],{"term-e\u002Fevent-driven":3,"related-e\u002Fevent-driven":59},{"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":53,"sitemap":54,"stem":57,"subcategory":6,"__hash__":58},"terms\u002Fterms\u002Fe\u002Fevent-driven.md","Event-driven",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 means services react to things that happen instead of constantly asking 'did anything change?' When a user signs up, an event fires. The email service hears it and sends a welcome email. The analytics service hears it and logs the signup. Nobody is polling — everyone is listening.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"Event-driven architecture is a design pattern where services communicate through events (messages describing something that happened) rather than direct calls. Services emit events to an event bus; other services subscribe and react. Promotes loose coupling, scalability, and extensibility.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"We moved to event-driven so services don't directly call each other.\" \u002F \"The OrderCreated event triggers three downstream processes.\"",{"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},"backend","Event-driven architecture means services react to things that happen instead of constantly asking 'did anything change?","intermediate","md","e",{},true,"\u002Fterms\u002Fe\u002Fevent-driven",[49,50,51,52],"Pub\u002FSub","Message Queue","Microservice","WebSocket",{"title":5,"description":41},{"changefreq":55,"priority":56},"weekly",0.7,"terms\u002Fe\u002Fevent-driven","E38Y68jNmUyrMfl7YXl61xql_QXY36NRNhOyX6R1D2c",[60,64,67,70],{"title":50,"path":61,"acronym":6,"category":62,"difficulty":42,"description":63},"\u002Fterms\u002Fm\u002Fmessage-queue","architecture","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":51,"path":65,"acronym":6,"category":40,"difficulty":42,"description":66},"\u002Fterms\u002Fm\u002Fmicroservice","Microservices is an architecture where instead of one big app, you have many tiny apps that each do one thing.",{"title":49,"path":68,"acronym":49,"category":62,"difficulty":42,"description":69},"\u002Fterms\u002Fp\u002Fpub-sub","Pub\u002FSub is like a newspaper service. Publishers write articles and drop them off.",{"title":52,"path":71,"acronym":6,"category":72,"difficulty":42,"description":73},"\u002Fterms\u002Fw\u002Fwebsocket","networking","WebSocket is like upgrading a walkie-talkie from push-to-talk to a full phone call.",1776518278066]