Recently Jnan Dash of Foldera made a great comment regarding persistence. He said there are two ways to park your car. The first is to disassemble it and store it on a shelf, then reassemble it when you need it again. Or just put it somewhere fully assembled.
SGen seems to be a straight forward Java language parser adding support for annotations.
Seems a wiki page has been devoted to describing CarrierWave.
As of late, I've been pondering the following questions, "How did we end up with the Application Server?" or "Is the middle tier just an effort to compensate for really bad persistence technology?"
In an interview, Victoria Livschitz touches on a problem that has been bothering me for some time. Notably, "The sequence of the routine itself -- what comes before what under what conditions based on what causality -- simply has no meaningful representation in OO, because OO has no concept of sequencing, or state, or cause."
A new release of CarrierWave was released today. It has updated support for Hibernate.
Here I make good on my previous promise to define a place in architecture for CarrierWave.
In short, if you could break up an orchestrated enterprise into one pattern, it would look alot like MVC. CarrierWave is the container for the Model, the 'system of record'.
Up to this point in time, CarrierWave has been mostly an experiment.
It was intended that the result of the experiment would live in the continuum between the application server and object database. To provide client side type safety for vertical clients, and enough meta-data for horiztontal clients. And to provide a level of isolation between client and server developers to help maintain a wait free development cycle.
