Layered Rails Architecture FAQs

Question 1

Where should business logic that spans multiple models go?

Accepted Answer

According to the Layered Rails pattern, multi-model orchestration belongs in the Application layer, typically implemented as a Service Object or an Interaction.

Question 2

When should I use Layered Rails instead of standard Rails MVC?

Accepted Answer

Use it when your models or controllers exceed 500 lines, when you have complex business operations involving multiple models, or when the domain logic becomes difficult to test in isolation.

Question 3

Can I use this skill alongside the dhh-coder skill?

Accepted Answer

Yes, it is designed to complement dhh-coder. You should default to DHH-style simplicity for standard CRUD and only reach for layered patterns when the specific domain complexity demands more structure.

Question 4

How does the Callback Scoring system work?

Accepted Answer

It rates model callbacks from 1 to 5. Internal data transformers score high (4-5) and stay in the model, while external side-effects like sending emails score low (1-2) and should be extracted to services.

Question 5

What is the Four-Layer Architecture in Rails?

Accepted Answer

It divides the application into Presentation (UI/HTTP), Application (Orchestration), Domain (Business Logic), and Infrastructure (Persistence/APIs) layers to prevent tight coupling and ensure data flows in one direction.

Layered Rails Architecture

Layered Rails Architecture

主要功能

使用场景

主要功能

使用场景