Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Asynchronous Service Oriented Design

Asynchronous Service Oriented Design

John Pignata

June 08, 2013
Tweet

More Decks by John Pignata

Other Decks in Programming

Transcript

  1. “Amazon.com started [in 1996] as a monolithic application, running on

    a Web server, talking to a database on the back end. This application evolved to hold all the business logic, all the display logic, and all the functionality that Amazon eventually became famous for. This went on until 2001 when it became clear that the front-end application couldn’t scale anymore.” http://queue.acm.org/detail.cfm?id=1142065 A Conversation with Werner Vogels
  2. Steve and Tara liked your message: Something pithy and funny

    about the current sporting event Steve and Tara liked your message: Rails is Benihana.
  3. picture a distributed log file that you can write to

    and tail from other services across the network
  4. “organizations which design systems ... are constrained to produce designs

    which are copies of the communication structures of these organizations”
  5. we pause if we exceed a threshold of remote failures

    to prevent compounding the problem
  6. QoS

  7. 18) Failure free operations require experience with failure. Recognizing hazard

    and successfully manipulating system operations to remain inside the tolerable performance boundaries requires intimate contact with failure. http://www.ctlab.org/documents/How%20Complex%20Systems%20Fail.pdf How Complex Systems Fail
  8. we prefer smaller building blocks like redis and kafka over

    message brokers like rabbitmq, qpid, etc