DEV Community: Leonardo Fragozo

📘 Refactoring with Service Objects in Ruby on Rails

Leonardo Fragozo — Thu, 01 May 2025 15:17:59 +0000

This tutorial documents two refactors applied in the ClinicSync project, a medical clinic management application developed as part of my MBA in Ruby on Rails. The goal was to apply architectural best practices using Service Objects to improve code readability, maintainability, and scalability.

What are Service Objects?

Service Objects are simple classes used to organize business logic that doesn't belong directly in models, controllers, or views.
They are a way to apply the Single Responsibility Principle (SRP) in practice, giving each part of the system a clearly defined role.

When to Use a Service Object

Use a Service Object when:

The logic is too complex to stay in the controller
The functionality doesn't naturally belong to a model
You need to reuse the same logic in multiple places
You want cleaner, more testable code

Basic Structure of a Service Object

class ExampleService
  def self.call(params)
    new(params).call
  end

  def initialize(params)
    @params = params
  end

  def call
    # main logic here
  end
end

Refactor 1: `AuthorizeUser` Service

Goal:

Remove repeated user type verification logic from the controllers.

Before:

def require_admin
  unless user_signed_in? && current_user.is_a?(Admin)
    redirect_to root_path, alert: "You are not authorized to access this page."
  end
end

After:

def require_admin
  unless user_signed_in? && AuthorizeUser.call(current_user, Admin)
    redirect_to root_path, alert: "You are not authorized to access this page."
  end
end

Service Created:

class AuthorizeUser
  def self.call(user, user_type)
    user.is_a?(user_type)
  end
end

Benefits:

DRY logic
Easier to maintain
Cleaner and reusable code

Refactor 2: `AuthenticateUser` Service

Goal:

Remove user authentication logic from SessionsController.

Before:

if (user = User.authenticate_by(params.permit(:email_address, :password)))
  start_new_session_for user
  redirect_to home_path_for(user), notice: "Logged in successfully."
else
  redirect_to new_session_path, alert: "Try another email address or password."
end

After:

user = AuthenticateUser.call(params[:email_address], params[:password])

if user
  start_new_session_for user
  redirect_to home_path_for(user), notice: "Logged in successfully."
else
  redirect_to new_session_path, alert: "Try another email address or password."
end

Service Created:

class AuthenticateUser
  def self.call(email_address, password)
    User.authenticate_by(email_address: email_address, password: password)
  end
end

Benefits:

Cleaner controller
Easy to extend for social login, 2FA, etc.
Clear separation of concerns

Conclusion

These two small Service Objects made the project:

Cleaner
More testable
Ready to scale

Service Objects are a powerful way to apply Clean Code and prepare your Rails application for future growth.

Written by: [Leonardo Quadros Fragozo]

📘 Refatorando com Service Objects no Ruby on Rails

Leonardo Fragozo — Thu, 01 May 2025 15:05:24 +0000

Este tutorial documenta dois refactors realizados no projeto ClinicSync, uma aplicação de gestão de clínicas médicas desenvolvida como parte do meu MBA em Ruby on Rails. O objetivo foi aplicar boas práticas arquiteturais utilizando Service Objects para melhorar a legibilidade, manutenção e escalabilidade do sistema.

O que são Service Objects?

Service Objects são classes simples usadas para organizar lógicas de negócio que não pertencem diretamente a models, controllers ou views.
Eles são uma forma de aplicar o princípio da Responsabilidade Única (SRP) na prática, deixando cada parte do sistema com um papel bem definido.

Quando usar um Service Object?

Use um Service Object quando:

A lógica é complexa demais para ficar dentro de um controller
A funcionalidade não pertence naturalmente a nenhum model
Você precisa reutilizar a mesma lógica em mais de um lugar
Quer escrever código mais limpo e fácil de testar

Estrutura básica de um Service Object

class NomeDoServico
  def self.call(params)
    new(params).call
  end

  def initialize(params)
    @params = params
  end

  def call
    # lógica principal aqui
  end
end

Refactor 1: `AuthorizeUser` Service

Objetivo:

Retirar dos controllers a lógica repetida de verificação de tipo de usuário.

Antes:

def require_admin
  unless user_signed_in? && current_user.is_a?(Admin)
    redirect_to root_path, alert: "You are not authorized to access this page."
  end
end

Depois:

def require_admin
  unless user_signed_in? && AuthorizeUser.call(current_user, Admin)
    redirect_to root_path, alert: "You are not authorized to access this page."
  end
end

Service criado:

class AuthorizeUser
  def self.call(user, user_type)
    user.is_a?(user_type)
  end
end

Benefícios:

Lógica DRY
Fácil de manter
Código mais claro e reutilizável

Refactor 2: `AuthenticateUser` Service

Objetivo:

Tirar do SessionsController a lógica de autenticação de usuário.

Antes:

if (user = User.authenticate_by(params.permit(:email_address, :password)))
  start_new_session_for user
  redirect_to home_path_for(user), notice: "Logged in successfully."
else
  redirect_to new_session_path, alert: "Try another email address or password."
end

Depois:

user = AuthenticateUser.call(params[:email_address], params[:password])

if user
  start_new_session_for user
  redirect_to home_path_for(user), notice: "Logged in successfully."
else
  redirect_to new_session_path, alert: "Try another email address or password."
end

Service criado:

class AuthenticateUser
  def self.call(email_address, password)
    User.authenticate_by(email_address: email_address, password: password)
  end
end

Benefícios:

Controller mais limpo
Fácil de expandir para login social, 2FA etc.
Separacão de responsabilidades clara

Conclusão

Esses dois pequenos Service Objects deixaram o projeto:

Mais limpo
Mais testável
Pronto para crescer

Service Objects são uma forma poderosa de aplicar Clean Code e preparar sua aplicação Rails para o futuro.

Escrito por: [Leonardo Quadros Fragozo]

Self Introduction — Ruby on Rails Developer | ClinicSync Project

Leonardo Fragozo — Sat, 26 Apr 2025 16:34:17 +0000

Hello! Nice to meet you.

My name is Leonardo Quadros Fragozo (but you can call me Leo), and I am a web application developer specializing in Ruby on Rails.

I am currently working on a project called ClinicSync, a medical clinic management platform that also serves as a record of my studies for the MBA in Ruby on Rails that I am currently taking.

📚 Areas of interest:

Ruby on Rails
Hotwire (Turbo + Stimulus)
TailwindCSS
Automated Testing (RSpec)

My goal is always to improve my technical skills and deliver well-structured and scalable solutions.

🚀 Check out my project ClinicSync on GitHub: GitHub - ClinicSync

Thank you very much for reading!

Apresentação — Desenvolvedor Ruby on Rails | Projeto ClinicSync

Leonardo Fragozo — Sat, 26 Apr 2025 16:31:01 +0000

Olá! Prazer em conhecê-los.

Meu nome é Leonardo Quadros Fragozo (mas você pode me chamar de Leo), e sou desenvolvedor de aplicações web com foco em Ruby on Rails.

Atualmente, estou desenvolvendo um projeto chamado ClinicSync, uma plataforma de gestão de clínicas médicas como parte do meu registro de estudos do MBA em Ruby On Rails que estou cursando.

📚 Áreas de interesse:

Ruby on Rails

Hotwire (Turbo + Stimulus)

TailwindCSS

Testes automatizados (RSpec)

Meu objetivo é sempre aprimorar meu conhecimento técnico e entregar soluções bem estruturadas e escaláveis.

🚀 Confira meu projeto ClinicSync no GitHub: GitHub - ClinicSync

Muito obrigado por acompanhar!

DEV Community: Leonardo Fragozo

📘 Refactoring with Service Objects in Ruby on Rails

What are Service Objects?

When to Use a Service Object

Basic Structure of a Service Object

Refactor 1: AuthorizeUser Service

Goal:

Before:

After:

Service Created:

Benefits:

Refactor 2: AuthenticateUser Service

Goal:

Before:

After:

Service Created:

Benefits:

Conclusion

📘 Refatorando com Service Objects no Ruby on Rails

O que são Service Objects?

Quando usar um Service Object?

Estrutura básica de um Service Object

Refactor 1: AuthorizeUser Service

Objetivo:

Antes:

Depois:

Service criado:

Benefícios:

Refactor 2: AuthenticateUser Service

Objetivo:

Antes:

Depois:

Service criado:

Benefícios:

Conclusão

Self Introduction — Ruby on Rails Developer | ClinicSync Project

Apresentação — Desenvolvedor Ruby on Rails | Projeto ClinicSync

Refactor 1: `AuthorizeUser` Service

Refactor 2: `AuthenticateUser` Service

Refactor 1: `AuthorizeUser` Service

Refactor 2: `AuthenticateUser` Service