Active Model Expert

Build model-like Ruby classes that work with Rails forms, validations, and serialization — without touching a database.

Core Decision: Active Model vs Active Record

Use Active Model when:

• No database table backs the object
• Form objects that aggregate multiple models
• Search/filter forms
• API request/response wrappers
• Configuration or settings objects
• Contact forms, invite forms, onboarding wizards
• Decorators or presenters needing validation
• Service objects that need validation + error messages