Staged event-driven architecture

<p>The staged event-driven architecture (SEDA) refers to an approach to <a href="/facts/Software_architecture/1Hokp0Ed">software architecture</a> that decomposes a complex, event-driven <a href="/facts/Computer_program/e38jH9N9">application</a> into a set of stages connected by queues. It avoids the high overhead associated with <a href="/facts/Thread_(computer_science)/hh8WHyPd">thread</a>-based <a href="/facts/Concurrency_(computer_science)/Ctnrrq4A">concurrency models</a> (i.e. locking, unlocking, and polling for locks), and decouples event and thread scheduling from application logic. By performing <a href="/facts/Admission_control/amEBodmQ">admission control</a> on each <a href="/facts/Event_queue/Kq7kX86w">event queue</a>, the service can be well-conditioned to load, preventing resources from being overcommitted when demand exceeds service capacity.
</p><p>SEDA employs <a href="/facts/Control_theory/aIuERpn6">dynamic control</a> to automatically tune runtime parameters (such as the scheduling parameters of each stage) as well as to manage load (like performing adaptive <a href="/facts/Load_Shedding/py7m5XeC">load shedding</a>). Decomposing services into a set of stages also enables modularity and <a href="/facts/Code_reuse/DVohfy6U">code reuse</a>, as well as the development of debugging tools for complex event-driven applications.
</p>

Staged event-driven architecture open-in-new

Staged event-driven architecture