Principal Programmer Jeffrey Hardy unpacks the Rails delegated type pattern that powers Basecamp and HEY.

37Signals, now known as Basecamp, shares  insights and practical advice on project management, remote work, collaboration, and productivity. Through blog posts, podcasts, and webinars, 37Signals offers strategies for effective communication, team coordination, and task management in distributed work environments. Readers can learn about project planning techniques, time management strategies, and leadership principles to foster a culture of collaboration and accountability within their teams. Additionally, 37Signals provides case studies, success stories, and real-world examples to inspire organizations to adopt a more flexible and efficient approach to work, driving productivity and innovation.

37signals Dev

The delegated types pattern in Rails enables scalable content management by separating metadata (recordings) from specific content (recordables). This architecture allows Basecamp to handle diverse content types—messages, documents, comments, uploads—through a uniform interface without constant rewrites. Key benefits include efficient copying (just pointer updates), unified querying across types, automatic feature inheritance for new content types, and simplified caching. The pattern uses immutable recordables with an event system for version history, organized in a tree structure with bucket-based access control. While it requires upfront learning and differs from standard Rails conventions, it dramatically reduces development time for new features and has powered Basecamp for over a decade without major architectural changes.

The Rails Recordables Pattern