Back to Course Domain Modeling in Ruby 0% Complete 0/0 Steps Domain Representation 9 Topics Naming Things: Headcount Decorator Decorator Transparency Surrogate Ordering Delegate Class Smart Collection Aggregate Boundaries Registry Handle Entities & Values 7 Topics Specific Whole Value Substitutable Whole Value Values Contextual Identity Part 1 Contextual Identity Part 2 From Hash to Value Object Prototype Pattern Persistence 13 Topics Mapper Aliasing Identity Map Ghost Load Extracting Ghost Load Virtual Proxy Self Save Part 1 Self Save Part 2 Self Save Part 3 Self Save Part 4 Macro Polymorphic Attributes in Rails - Part 1 Polymorphic Attributes in Rails - Part 2 External Resources 2 Topics Caching Gateway Cache Rot Logic & Workflow 6 Topics Workflow Complex Predicate Audited Predicate Advanced Audited Predicate Rule Table Sagas Presentation 3 Topics Presenter Object Presenter and View Display Builder Conclusion and Next Steps Search (Entire Site)Search Domain Modeling in Ruby Persistence Self Save Part 1 Module 3, Topic 7 In Progress ← Previous Next→ Self Save Part 1 Module Progress 0% Complete The start of a series answering the question: why shouldn't a domain model object save itself? Oop, this content isn't available to visitors. Please register or log in to continue! Or you could purchase this course. Responses You must be logged in to post a comment.
Responses