Filed under Architecture, Design

Some thoughts about O/RMs.

1. The Mappings: Whether it’s rolled via XML, attributes, or some fluent API, it’s something you as a developer have to maintain, so even if you let the conceptual object-model drive the design of your database, you are implicitly DDL through the mappings. 2. HQL, EQL, XQL: It is just a DSL over SQL, which … Continue reading »

Where are your Scenarios in your domain?

If you design your entities before you design your scenarios, you are data-driven! The Scenarios are primary – The entities are secondary! – Daniel Wertheim My words of what I think is wrong in many projects, and thats what this post is about. Definition of Scenario a postulated sequence of possible events – http://wordnetweb.princeton.edu/perl/webwn?s=scenario In … Continue reading »

NHibernate – Repository pattern

I know that there allready are implementations for NHibernate-based repositories (eg. RhinoTools) but I can’t help to fiddling a bit with a design that I feel comfortable with. When building business applications I like to use a domain model (Read more – Martin Fowler) and to use repositories (Read more – Martin Fowler) for storing … Continue reading »