I am in the process of reading Rocky Lhotka's book, entitled "Expert
One-on-One Visual Basic .NET Business Objects.  In this book, Rocky defines
a set of goals for a .NET distributed application architecture, and then he
designs and builds a reusable framework that realizes those goals.  After
reading the first two chapters, my impressions are very favorable.  The book
is extremely well-written, and Rocky's line of reasoning is very well
documented.

The approach to .NET distributed application architecture that Rocky takes
is very object-oriented.  Business objects that encapsulate both data and
business rules are instantiated and moved from physical tier to physical
tier as necessary using .NET remoting.

This approach seems to stand in stark contrast to te approach that I read
about much more often in the .NET literature, which is the data-centric,
message-based approach.  I have seen threads in the past that compared these
two approaches, but I am curious about what the current thinking is.  Which
of these appraches to architecture lends itself better to the
service-oriented architecure that seems to be growing in popularity?

Has anyone read Rocky's book and tried his approach?

Does anyone have a strong preference for either the OO approach or the
data-centric approach?