BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ
News Articles Presentations Podcasts Guides

Topics

Choose your language

QCon New York

Find real-world practical inspiration from the world’s most innovative software leaders. Attend in-person.
QCon San Francisco

Learn what's next in software from world-class leaders pushing the boundaries. Attend in-person or get video-only pass to recordings.
The Software Architects' Newsletter

Your monthly guide to all the topics, technologies and techniques that every professional needs to know about. Subscribe for free.

InfoQ Homepage News InfoQ Article: Using SEDA to Ensure Service Availability

Building an Efficient Cloud Application Architecture (Live Webinar June 22, 2023) - Save Your Seat

InfoQ Article: Using SEDA to Ensure Service Availability

Bookmarks

Oct 12, 2006 less than one minute

Write for InfoQ

Join a community of experts. Increase your visibility.
Grow your career.Learn more

SEDA is a new strategy for incorporating event driven architecture for scalability and availability of services in the context of SOA. These strategies are based on queuing research pioneered for the use of highly abailable and scalable services, initially in the Web context, but moving into the SOA and Web services context. This article describes SEDA with an implementation in the context of Mule.

Read Using SEDA to Ensure Service Availability.

In SEDA, a request to system or service can be split in to a chain of stages each doing its part of the total workload of the request. Each stage is connected to the others by request queues, and by controlling the rate at which each stage admits requests, the service can perform focused overload management (for example, by filtering only those requests that lead to resource bottlenecks). By choosing this approach a given computer system can scale very well without having the traditional pile of CPU capacity to handle request bursts.

Rate this Article

Adoption
Style

This content is in the Architecture topic

Related Topics:

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • New?

    by ashok shetty,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    SEDA is a new strategy for incorporating event driven architecture for scalability and availability of services in the context of SOA.

    New?? Hmmm, I recall hearing about it in 2003/2004 when I was developing a low latency, high thro'put server component using Proactor,Reactor pattern.

    SEDA hijacked by SOA.. i mean in context of SOA might be new.

    Mule was around before that SOA Borg started assimilating everything.

    And yes, Mule rocks!

    Back to top
  • Re: New?

    by Cameron Purdy,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    SEDA is definitely not new, but it's newer than say CORBA ;-)

    The concepts are very good, but not for the reasons given. It mainly has to do with the limitations of scalability of the ACID model, particularly with "I" of read-committed or above.

    We use the queued concepts extensively within our Coherence infrastructure, which allows us to achieve and sustain the maximum theoretical network throughput on Gigabit Ethernet -- and that is using pure Java!

    However, the benefits to application developers will be even greater, as these "low level" concepts begin to surface in standards for work flow management, staged transactions, etc.

    Peace,

    Cameron Purdy
    www.tangosol.com/

    Back to top
  • Re: New?

    by Rune Schumann,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Ehmm...
    The term "new" was actually added by the editors...

    Yes I´m totally aware of that the SEDA concept is not new. Some of the ideas actually origines back to the grandfather of OO, Kristen Nygaard at the University of Oslo, Norway (great university :-D).
    He actually introduced these ideas of processing stages. Øystein Haugen and Birger Møller Pedersen (the UML 2.0 guys, you know!) wrote a paper about this thingy they called (surprise!) STAGE. This mist be way back in the nineties...

    So guys, sorry for the editor´s "add-on"...

    Rune Schumann

    Back to top
  • Re: New?

    by Billy Newport,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    WebSphere XD's on demand router does this but for HTTP, JMS and IIOP calls. It's also integrated with our placement to add/remove JVMs/applications depending on load as well as using service level agreements for how to deliver queued events to meet those goals. Nothing really new, but cool.

    Back to top
  • Re: New?

    by aravind yarram,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    websphere sucks!!!

    Back to top

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT