backend-anti-patterns

Common backend anti-patterns in Ruby on Rails include placing business logic in models instead of persistence, and misplacing authorization in operations rather than controllers. This skill documents these issues to guide developers toward cleaner, more maintainable code.

Authorization in Rails should be performed at the controller level, not within operations. By separating concerns and keeping authorization in controllers, you ensure more secure and maintainable backend code, avoiding common architectural anti-patterns.

You can use code reviews to enforce backend best practices by checking if models contain business logic instead of persistence, or if authorization is misplaced. This skill serves as a guide to quickly identify violations and apply correct architectural alternatives.

Using contracts for validation is a recommended best practice for Rails backend development. This skill outlines correct alternatives to anti-patterns, guiding you to separate concerns and use contracts to ensure robust and maintainable code.

You need to separate concerns in backend models and operations when models start containing business logic instead of persistence. This skill helps identify such anti-patterns and provides correct alternatives to ensure secure and maintainable code.