Staged event-driven architecture

The staged event-driven architecture (SEDA) refers to an approach to software architecture that decomposes a complex, event-driven application into a set of stages connected by queues.[1] It avoids the high overhead associated with thread-based concurrency models, and decouples event and thread scheduling from application logic. By performing admission control on each event queue, the service can be well-conditioned to load, preventing resources from being overcommitted when demand exceeds service capacity.

SEDA employs dynamic control to automatically tune runtime parameters (such as the scheduling parameters of each stage) as well as to manage load (like performing adaptive load shedding). Decomposing services into a set of stages also enables modularity and code reuse, as well as the development of debugging tools for complex event-driven applications.

See also

References

  1. "SEDA: An Architecture for Highly Concurrent Server Applications". Harvard University. Retrieved 2013-09-03. SEDA is an acronym for staged event-driven architecture, and decomposes a complex, event-driven application into a set of stages connected by queues.

Bibliography

External links

This article is issued from Wikipedia - version of the 1/29/2014. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.