CRUD in 30 minutes
Generate a Post resource, run migrations, and implement create/read/update/delete with validation for title presence.
Backend & Runtime / Knowledge library
Ruby on Rails (Rails)
opinionated mvc framework for web backends
Why learn Ruby on Rails (Rails)?
Rails helps teams ship database-backed web apps fast by giving strong conventions for routing, data modeling, views, testing, and deployment workflows.
Where it came from
Rails was created by David Heinemeier Hansson and open-sourced in 2004 from Basecamp work. It popularized Convention over Configuration and DRY in web development. Rails 3 incorporated Merb ideas and a more modular architecture. Rails 5 added API mode and Action Cable for websockets. Rails 7 made Hotwire/Turbo default for modern low-JS interactivity.
- Rails was created by David Heinemeier Hansson and open-sourced in 2004 from Basecamp work.
- It popularized Convention over Configuration and DRY in web development.
- Rails 3 incorporated Merb ideas and a more modular architecture.
- Rails 5 added API mode and Action Cable for websockets.
- Rails 7 made Hotwire/Turbo default for modern low-JS interactivity.
Build your understanding
Work through these exercises in order. Try the task before opening a reference.
- Generate a Post resource, run migrations, and implement create/read/update/delete with validation for title presence.
- Add authentication, then restrict edit/delete so users can modify only their own posts. Write request specs for access control.
- Send a welcome email using Active Job and queue adapter. Add retries and test that the job enqueues after user signup.
- Build real-time comments on a post using Turbo Streams. Ensure new comments appear without full page reloads.
- Find and remove an N+1 query in an index page using includes/preload. Measure before/after in logs.
More ways to practice
Auth + ownership
Add authentication, then restrict edit/delete so users can modify only their own posts. Write request specs for access control.
Background processing
Send a welcome email using Active Job and queue adapter. Add retries and test that the job enqueues after user signup.
Turbo-powered comments
Build real-time comments on a post using Turbo Streams. Ensure new comments appear without full page reloads.
query tuning
Find and remove an N+1 query in an index page using includes/preload. Measure before/after in logs.
Documentation and sources
- Official Rails site (rubyonrails.org)
- Rails Guides (guides.rubyonrails.org)
- Getting Started Guide (guides.rubyonrails.org)
- Rails API Docs (api.rubyonrails.org)
Catalog research notes
- Rails 8.0 (2024) pushed an even more batteries-included full-stack setup.
- Solid Queue, Solid Cache, and Solid Cable became core-friendly choices for jobs, cache, and realtime.
- New app generation improved secure defaults and developer onboarding.
- Hotwire/Turbo-centered server-rendered interactivity remains a primary Rails path.
Connect the ideas
Explore next
Real World Example
Streamlining Subscription Management for Boutique SaaS
A boutique SaaS provider managing recurring billing for niche software tools.
The business problem
Manual database schema management and fragmented controller logic lead to inconsistent billing states and high maintenance costs when adding new subscription tiers.
How this topic solves it
Ruby on Rails utilizes the Active Record pattern to encapsulate business logic directly within models, ensuring that state transitions for subscriptions are consistent and automatically mapped to the underlying database schema.
- Define the Subscription model using Active Record to encapsulate billing state logic.
- Configure routes to map subscription endpoints to the SubscriptionController.
- Implement controller actions to process incoming subscription requests and parameters.
- Use model callbacks to trigger asynchronous background jobs for billing updates.
- Render subscription views using Action View to display current status to users.
Shows the relationship between users, their subscriptions, and the billing events triggered by model changes.
id, name, email
id, status, user_id
id, subscription_id, status
- User → has_many (1:N) → Subscription
- Subscription → triggers (1:N) → DeliveryJob
Implementation example
This code demonstrates how Rails encapsulates business logic within the model, using callbacks to trigger background jobs automatically when a subscription state changes.
class Subscription < ApplicationRecord
belongs_to :user
# Encapsulates state logic within the model
after_save_commit :process_billing, if: :active?
def process_billing
BillingJob.perform_later(self)
end
endExpected business outcome
A unified, maintainable codebase where business rules are centralized, reducing the risk of data corruption during subscription lifecycle changes.
Limitations and checks
The tight coupling of business logic to models can lead to 'fat models' that become difficult to test as the application grows; verify this by monitoring the cyclomatic complexity of model methods.