Question 1

Is Rails dead? Why choose Rails over Node.js or Django in 2026?

Accepted Answer

Rails is not dead — it's mature. Greenfield adoption has declined (Node/Python growing), but Rails powers 2M+ production apps. Choose Rails for: rapid MVPs, SaaS products, teams prioritizing speed-to-market, existing Rails monoliths, Ruby's elegance. Skip Rails for: real-time systems (use Node), machine learning (use Python), or distributed microservices (use Go/Rust). For startups, Rails remains the fastest path to revenue.

Question 2

What is Hotwire (Turbo + Stimulus) and when should I use it?

Accepted Answer

Hotwire brings modern UX to server-rendered Rails without JavaScript complexity. Turbo replaces Turbolinks: AJAX page updates, prefetching, morphing. Stimulus provides lightweight interactivity (modals, dropdowns, carousels) without a heavy SPA framework. Use Hotwire when: building traditional Rails apps but want fast, snappy UX. Skip it when: building a single-page app (use React/Next.js) or real-time collaboration (use WebSockets + Node).

Question 3

Should I build a monolith or microservices with Rails?

Accepted Answer

Monolith first (95% of startups should). Rails monoliths scale to billions of requests (GitHub, Shopify). Microservices = premature complexity; split only when: single team can't own one codebase, scaling bottlenecks emerge, or domain boundaries are clear. Most Rails refactors fail because they start with services. Extract a service when you have data to prove it, not before.

Question 4

What are ActiveRecord pitfalls and how do I avoid N+1 queries?

Accepted Answer

N+1: fetching related records in loops (e.g., `@users.each { |u| u.posts.size }`). Fix: eager-load with `.includes(:posts)` or `.left_outer_joins(:posts)`. Monitor with tools like Bullet gem in dev. Other pitfalls: missing indexes (use `explains`), overfetching columns (use `.select`), large transactions, and callback hell. Solution: indexes, eager loading, service objects, database query profiling.

Question 5

How do I handle authentication and authorization in Rails?

Accepted Answer

Standard gems: Devise (authentication, sessions, password reset) + Pundit (authorization, policy objects). For APIs: Devise-JWT or token-based auth. For simple apps: build auth yourself (Rails has `authenticate_with_password` helpers). Avoid: rolling your own crypto; use Devise. For OAuth (Google/GitHub login): use omniauth-google2 or similar. Multi-tenant: add account_id to all models, use Pundit policies to scope by tenant.

Question 6

What performance optimizations matter most in Rails?

Accepted Answer

Top 3: (1) Database indexes — query profiling finds 80% of bottlenecks. (2) Caching — Redis + fragment/page caching, cache_key versioning. (3) Background jobs — move slow work to Sidekiq. Measure: New Relic/Datadog for APM, Bullet for N+1, rails_panel in dev. Avoid premature optimization; profile first, optimize second.

Question 7

What is the Rails hiring market like?

Accepted Answer

Demand: strong. Salaries: $120-170k mid-level (vs. $140-180k Node). Growth: slower than Node/Python, but steady. Best opportunities: startups (rapid growth), SaaS (established), agencies (contract work). Junior Rails roles scarce (everyone wants mid+, less bootcamp pipeline than JavaScript). Best path: freelance → SaaS team → lead engineer. Rails skills = senior title faster (5-7 yrs vs. 8-10 yrs for Node).

Region	Junior	Mid	Senior
USA	$90k	$140k	$185k
UK	£55k	£85k	£115k
EU	€60k	€90k	€125k
CANADA	C$100k	C$155k	C$205k

Ruby on Rails

What is Ruby on Rails

📋 Before you start

💰 Salary by region

🎓 Certifications

⚖ Compare with

❓ FAQ

Not sure this skill is for you?

Find your ideal career path