Very nice intro to microarchitechtures, Wojciech, and I believe a correct assumption that Cairngorm is the one to choose.

However I want to advocate the use of PureMVC. I tried to use a “semi-Cairngorm” approach on my latest project and having only mediocre knowledge of how Cairngorm works it took me too much time to wrap my head around it entirely. Maybe it’ll help if you could publish a hands on example made in Cairngorm.
I have now tried to make an ideal small-app in Pure-MVC and I find the concept of MVC-Facade much easier to grasp than the MVC-Service logic (This of course since I know the Facade pattern better ) I like the strict use of mediators and proxies, the way you kind of information-hide all the VO/TDOs known from Cairngorm.
The main critique of pure-MVC is that the strict-typing of retun values from proxies is gone, all you get is generic objects. This is a big flaw since you loose the ability ty type-check return values. You’ll need to know what comes back. However  I feel the same problem is present in the Cairngorm’s VOs as well? Or am I wrong.
Pure-MVC has scheduled a new release “soon” and I am curious of what to expect. If they address the few flaws they have now it’ll sail up as the best cross-language microarchitechture to use, since Pure-MVC is now language-transparent (ie .Net-compatible and SilverLight-compatible). Cairngorm is currently bound to ActionScript (AS3).
However… the word on the net is that “if you’re gonna use a microarchitechture…use Cairngorm”, so one day soonI’m gonna make an effort and use it