DDD 屏幕投射问题？
前几天，我观看了 Greg Young 在 DDD 上的截屏，其中谈到持久化对象的所有状态转换，而不是保存时的状态，然后加载它“重放”所有这些消息以恢复当前状态。似乎是一个非常有趣的想法，但我不知道这个特殊的东西叫什么！我想了解更多有关它的信息，但如果没有它的真实名称，我很难获得任何像样的结果。
谁能启发我吗？
屏幕截图是@ http://www.infoq.com/presentations/greg-年轻的unshackle-qcon08
I wathced a screen cast on DDD by Greg Young the other day which spoke about persisting all state transitions of an object, instead of it's state when saved, then to load it "replay" all these messages to get the current state back.. This seemed like a really interesting idea, but I'm stuck as to what this particular thing is called! I'd like to read more about it, but I'm having trouble getting any decent results without a real name for it.
Can anyone enlighten me?
screen cast is @ http://www.infoq.com/presentations/greg-young-unshackle-qcon08
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
迈克尔·佩里 (Michael Perry) 的评论将其称为历史建模。
他还表示，他“为历史建模定义了一套规则和框架：”并提供了几个链接：（我没有足够的代表来发布它们）
http://correspondence.codeplex.com/
我个人没有研究或使用过状态转换模型，但听起来确实很有趣。
The comment by Michael Perry calls it Historic Modeling.
He also says that he has "defined a set of rules and a framework for Historic Modeling:" and provides a couple links: (I don't have enough rep to post them both)
http://correspondence.codeplex.com/
I haven't personally studied or used state transition models, but it does sound interesting.
Martin Fowler 将此称为事件溯源。 Greg Young 甚至引用了 Fowler 在他的分布式域驱动设计系列中，其中他澄清了有关演示的一些细节；你可能想读一下。
Martin Fowler calls this Event Sourcing. Greg Young even references Fowler in his series on Distributed Domain Driven Design, in which he clarifies some details regarding the presentation; you might want to read it.
稍微偏离了切线...Rocky Lhotka 在他的 CSLA 业务对象框架 但这仅适用于内存中的更改历史记录，并且（据我所知）不会持久保存到数据库中。
DDD 人们往往不太重视 CSLA，但其中包含的一些想法和实现绝对值得研究。
Slightly off on a tangent... Rocky Lhotka has implemented something he calls n-level undo (elsewhere referred to as Multilevel Undo) in his CSLA Business Object framework but this only applies to history of changes in memory and (that I'm aware of) doesn't persist down into the DB.
DDD folks tend not to think very highly of CSLA but some of the ideas and implementations contained therein are definitely worth looking into.