A common critique of Rails is that it encourages a poor separation of concerns. That when things get serious, you need an alternative that brings the missing pieces. We disagree.

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

The Domain Driven Design (DDD) book discusses four conceptual layers: presentation, application, domain, and infrastructure. The application layer implements business tasks by coordinating work with the domain layer. For copying, Recording::Copyable creates a new Copy record. Filing is a common parent class for both the copy and move operations. The SRP violation we care more about is violation at the implementation level.

Vanilla Rails is plenty

We don’t distinguish application and domain layers

Controllers access domain models directly

The dangers of isolating the application layer