i 1626d02862e55744 by {CHB Books}

Author:{CHB Books}
Language: eng
Format: epub
Published: 2009-01-26T16:54:46+00:00

Say goodbye to the good old predictive call-stack architecture, where you get

to define what happens when and in what order. Instead, be ready to respond

to events at any time in any order, regaining your context as needed. Make

asynchronous requests concurrently instead of calling methods one by one.

Avoid complete chaos by modeling your application using event-driven pro-

cess chains or state models. Reconcile errors through compensation, retry, or

tentative operations.

Sounds scary and more than you bargained for? Luckily, the real world has

to deal with the same issues for a long time: delayed letters, broken prom-

ises, messages crossing in transit, payments posted to the wrong account—the

examples are countless. Accordingly, people had to resend letters, write off bad

orders, or tell you to ignore the payment reminder in case you already sent a

payment. So don’t just blame the real world for your headaches, but also use it

as a place to look for solutions. After al , Starbucks does not two-phase com-

mit, either.1 Welcome to the real world.

Gregor Hohpe is a software architect with Google, Inc. Gregor is a widely rec-

ognized thought leader on asynchronous messaging architectures and service-

oriented architectures. He coauthored the seminal book Enterprise Integration

Patterns (Addison-Wesley Professional) and speaks regularly at technical

conferences around the world.

1 See http://www.eaipatterns.com/ramblings/18_starbucks.html.

Collective Wisdom from the Experts

95

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.