Serializers (Active Model Serializers) in Ruby on Rails - Step-by-Step Execution

Concept Flow - Serializers (Active Model Serializers)

Controller receives request

↓

Fetch model data from DB

↓

Pass model to Serializer

↓

Serializer formats data

↓

Render JSON response

↓

Client receives formatted JSON

The controller gets data, sends it to the serializer, which formats it into JSON, then sends it back to the client.

Execution Sample

Ruby on Rails

class UserSerializer < ActiveModel::Serializer
  attributes :id, :name, :email
end

Defines a serializer that formats User objects to include only id, name, and email in JSON.

Execution Table

Step	Action	Input Data	Serializer Output	Notes
1	Controller fetches User with id=1	User(id=1, name='Alice', email='[e-mail]', password='secret')	N/A	Raw model data fetched from DB
2	Pass User to UserSerializer	User object	UserSerializer instance created	Serializer prepares to format data
3	Serializer reads attributes	User object	{"id":1, "name":"Alice", "email":"[e-mail]"}	Only specified attributes included
4	Render JSON response	Serialized JSON	{"id":1, "name":"Alice", "email":"[e-mail]"}	Client-ready JSON sent
5	Client receives JSON	JSON string	Parsed JSON object	Client can use data easily

💡 Serialization completes after JSON is rendered and sent to client

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
user	nil	User(id=1, name='Alice', email='[e-mail]', password='secret')	Same User object	Same User object	Same User object
serialized_json	nil	nil	nil	{"id":1, "name":"Alice", "email":"[e-mail]"}	{"id":1, "name":"Alice", "email":"[e-mail]"}

Key Moments - 2 Insights

Why does the password not appear in the JSON output?

Because the serializer only includes attributes explicitly listed (:id, :name, :email), so password is excluded as shown in step 3 of the execution_table.

What happens if the model has nil values for attributes?

The serializer includes the attribute with a null value in JSON, since it serializes the attribute as is, visible in step 3 if any attribute is nil.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what attributes are included in the serialized JSON?

A name, email

B id, name, email

C id, name, email, password

D All user attributes

💡 Hint

Check the 'Serializer Output' column at step 3 in the execution_table

At which step does the serializer create the JSON string?

A Step 3

B Step 1

C Step 2

D Step 4

💡 Hint

Look at the 'Serializer Output' column where JSON string first appears

If you add :created_at to attributes in the serializer, what changes in variable_tracker after step 3?

A serialized_json becomes nil

B user variable changes to include created_at

C serialized_json includes created_at attribute

D No change in serialized_json

💡 Hint

Adding attributes affects serialized_json output, check variable_tracker's serialized_json row

Concept Snapshot

Active Model Serializers format Rails models into JSON.
Define attributes in serializer class.
Controller passes model to serializer.
Serializer outputs JSON with only listed attributes.
Excludes sensitive data by omission.
Used to cleanly shape API responses.

Full Transcript

In Rails, Active Model Serializers help convert model objects into JSON format for APIs. The controller fetches data from the database, then passes the model instance to the serializer. The serializer reads only the attributes you list and creates a JSON string with those values. This JSON is then sent back to the client. For example, if you have a User model with many fields, but only want to expose id, name, and email, you list those in the serializer. Passwords or other sensitive data are not included unless explicitly added. This process ensures your API responses are clean and safe. The execution table shows each step: fetching the user, creating the serializer, generating JSON, and sending it to the client. Variables like the user object stay the same, but the serialized_json variable changes from nil to the JSON string after serialization. This helps beginners see exactly how data flows and changes during serialization.