My company has recently started using Agatha (http://davybrion.com/blog/category/agatha/) as a business framework for some prototype work. It's really new (read: not mature) and I have some reservations about using it as opposed to a framework such as CSLA that has a lot of years behind it.
Agatha seems to offer a lot in the dependency injection/IOC arena. In other ways it seems to mirror a lot of the functionality I see in CSLA.Net.
Unfortunately my knowledge of CSLA is only book knowledge at this point as I have been evaluating it along with other frameworks so I'm hoping that someone can shed some light on the pros and cons of Agatha vs. CLSA.
I found my answer: Neither.
After some serious discussions and a lot of reading I have come to the conclusion (whether wrong or right) that Agatha and CSLA both embrace what appears to be the "Loosey Goosey" SOA anti-pattern (http://msdn.microsoft.com/en-us/library/ms954638.aspx).
I'm a big fan of many of the features that CSLA offers. It's possible that it offers something like versioned objects or other features that I don't know about. But I think that solid N-Tier architecture involves service contracts.
I'd be happy to be proved wrong or hear the insight of others with more experience.
No, CSLA does not embrace the "Loosey Goosey" pattern.
You should read these threads first:
plus there is more info in the CSLA FAQ
Thanks for your response and the links to that information.
Copyright (c) Marimer LLC