Even though I should wait for your draft before discussing. After spending some time with Udi's Command Query responsibility segregation here<http://skillsmatter.com/podcast/open-source-dot-net/udi-dahan-command-query-responsibility-segregation>. I couldn't help but think that document databases were a perfect fit for the view model persistent storage i.e. the query. Continuing to use a relational model for asynchronous commands sent as messages on a bus, but that the relational database would be the "truth", and everything should be derivable and persisted from it in a document database specific for the screens that use the information. Then the choice becomes how often should the document database be synchronized. This makes for a good argument for using Rhino-ETL for the occasional synchronization, and event messages sent via Notify for more real-time synchronization. Am I way off base?
-- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
