DCI (data, context, interaction) persistence example

views:

answers:

+1 Q:

DCI (data, context, interaction) persistence example

All the examples of DCI I've seen seems to be based on the object as the ultimate holder of information, and the transaction boundaries are defined inside the methods.

I would like to see an example of a persistent application, where there is some sort of persistence layer, i.e. where there can be duplicate object copies of the underlying persistence storage and where a change to an object is a change to a copy that will later be persisted. Does DCI work for that model at all?

DCI doesn't really concern itself with persistance.

Guge 2010-08-27 05:55:44

What does that mean? That it's an orthogonal concern, i.e. DCI is outside that scope, because it doesn't matter? Or it's a valid concern that is just not addressed by DCI?

nilskp 2010-08-27 12:54:44

Persistance is always a valid concern, but DCI is more of a paradigm than an architecture. So I think it's orthogonal. DCI has a lot to say about data, but not so much where it comes from or where it goes. I guess you could even use DCI in your persistance layer, in the sense that persisting data is a use-case that begins when the user selects File/Save from the menu.

Guge 2010-08-27 14:38:40

At http://blog.maxant.co.uk/pebble/files/dci_java_example_for_object_composition_google_group_201010052226.zip I have posted an example in Java, which incorporates JPA (ORM) for persisting entities.

It's part of a white paper to be posted soon at www.maxant.co.uk/whitepapers.jsp

A further example showing DCI being integrated into an app server will be in that paper. Hope that helps!

Ant Kutschera 2010-10-08 18:41:55

ansaurus

tags:

views:

answers:

DCI (data, context, interaction) persistence example

related questions