Sorcery and Patterns in Ruby
summary
A short RailsClub talk about using the Sorcery authentication gem (a lightweight alternative to Devise) and applying object-oriented design patterns in Ruby/Rails. It covers practical use of patterns such as Service Object, Value Object, and Query Object to improve readability and maintainability, explains why Sorcery is a good choice for authentication, and shows how to avoid excessive ActiveRecord callbacks by designing a cleaner application architecture around authentication.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 2:59Devise callbacks problems
- 5:35Service objects in Sorcery
- 7:07Optimizing core models
- 9:17Modern Rails patterns
- 10:00Conclusion and Q&A
related talks
30mRuby Techniques by Example
41mAPPLICATION ARCHITECTURE: BOUNDARIES, OBJECT ROLES, & PATTERNS
36m"Business Logic in Ruby"
32mN design patterns you might actually use
38mRefactoring Fat Models with Patterns
35mRails vs. Object Oriented Design
30mSorbet at Grailed: Typing a Large Rails Codebase to Ship with...
33mRails is Just Ruby