For the record, I agree that events can be at the highest levels of
the architecture. Services are what you do, events are triggers for
doing things, and processes are how you do them.
-tb
Todd Biske
http://www.biske.com/blog/
Sent from my iPhone
On Feb 19, 2010, at 9:44 AM, reamon943 <[email protected]> wrote:
--- In [email protected], Gregg
Wonderly <ge...@...> wrote:
>
> The simple issue is that the use of the term RPC (perhaps RPC-like
> would make it less implementation like) is still being taken as an
> "implementation" rather than an "architectural" mechanism.
I understand the pain. I encountered the same issue when promoting
the notion that EDA could be applied to the highest levels of
architecture--but most felt it only made sense as an implementation
detail. I couldn't convince many (any?) that looking at significant
events would be a worthwhile exercise and that EDA != pub/sub.
-Rob
