Attention: We are retiring the ASP.NET Community Blogs. Learn more >

Data in distributed systems

Putting code and data into a single thing is a bad idea for distributed systems. Behavior is bound to the role that data plays in a functional scope. Presentation is a scope, calculation, combination, aggregation and validation are scopes, services and resource access is a scope. Having all code for all scopes on a single thing is bad. (...)

 
I agree with Clemens, and this is somehow related to my last posts on exposing your business logic layer, and to an old thread in the blogsphere.
 

No Comments