Why Ruby on Rails exists - Performance Evidence

Performance: Why Ruby on Rails exists

MEDIUM IMPACT

Ruby on Rails affects how quickly a web application can be developed and how efficiently it handles server-side rendering and database interactions.

Building a web app quickly with maintainable code

Ruby on Rails

Using Rails conventions like ActiveRecord for database and ERB for views

Speeds up development with reusable code and optimized query generation.

📈 Performance GainReduces server response time by avoiding redundant queries and improves developer productivity.

Building a web app quickly with maintainable code

Ruby on Rails

Manually writing all SQL queries and HTML templates without a framework

This leads to slow development, more bugs, and inconsistent code structure.

📉 Performance CostBlocks development speed and increases risk of inefficient queries causing slow server response.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Manual SQL + HTML	Minimal but inefficient queries	N/A (server-side)	N/A (server-side)	[X] Bad
Rails with ActiveRecord + ERB	Efficient queries generated	N/A (server-side)	N/A (server-side)	[OK] Good

Rendering Pipeline

Rails handles server-side rendering by processing requests, querying the database, rendering HTML, and sending it to the browser.

→Server Processing

→Database Query

→HTML Rendering

→Network Transfer

⚠️ BottleneckDatabase Query and Server Processing can be slow if queries are not optimized or code is inefficient.

Optimization Tips

1Rails speeds development by using conventions and reusable components.

2Server-side rendering in Rails affects initial load time based on backend efficiency.

3Optimize database queries and use caching to improve Rails app performance.

Performance Quiz - 3 Questions

What is a main reason Ruby on Rails was created?

A To speed up web app development with conventions

B To replace all frontend JavaScript frameworks

C To eliminate the need for databases

D To make websites load instantly without servers

DevTools: Network and Performance panels

How to check: Use Network panel to measure server response time and Performance panel to see time spent rendering HTML.

What to look for: Look for long server response times or slow HTML delivery indicating backend bottlenecks.

Practice

1. Why was Ruby on Rails created?
Rails helps developers by:

easy

A. Forcing developers to write all code manually

B. Providing tools to build web apps faster and easier

C. Replacing the need for databases in web apps

D. Making Ruby code run faster than other languages

Solution

1. Step 1: Understand Rails purpose

   Rails was designed to speed up web app development by giving ready-made tools and structure.

2. Step 2: Evaluate options

   Only Providing tools to build web apps faster and easier matches this goal. Options A, B, and C are incorrect because Rails does not force manual coding, does not make Ruby faster, and does not replace databases.

3. Final Answer:

   Providing tools to build web apps faster and easier -> Option B

4. Quick Check:

   Rails helps build apps faster = D [OK]

Hint: Rails is about speed and ease in web development [OK]

Common Mistakes:

• Thinking Rails makes Ruby faster
• Believing Rails removes databases
• Assuming Rails requires manual coding

2. Which of these is a correct way to start a new Rails project in the terminal?

easy

A. rails new myapp

B. ruby create myapp

C. rails start myapp

D. ruby new project myapp

Solution

1. Step 1: Recall Rails project creation command

   The standard command to create a new Rails app is rails new appname.

2. Step 2: Check options

   Only rails new myapp matches the correct syntax. Others use wrong commands or order.

3. Final Answer:

   rails new myapp -> Option A

4. Quick Check:

   rails new appname = A [OK]

Hint: Remember: 'rails new' starts a new project [OK]

Common Mistakes:

• Using 'ruby' instead of 'rails' to create projects
• Mixing command order
• Using 'start' instead of 'new'

3. What will happen when you run rails server in a Rails project folder?

medium

A. It installs Ruby on your computer

B. It deletes the project files

C. It starts a web server to run your app locally

D. It opens a database management tool

Solution

1. Step 1: Understand 'rails server' command

   This command launches a local web server so you can see and test your app in a browser.

2. Step 2: Evaluate options

   Only It starts a web server to run your app locally describes this behavior. Others describe unrelated or incorrect actions.

3. Final Answer:

   It starts a web server to run your app locally -> Option C

4. Quick Check:

   rails server runs local web server = C [OK]

Hint: 'rails server' runs your app locally in browser [OK]

Common Mistakes:

• Thinking it deletes files
• Confusing it with Ruby installation
• Assuming it opens database tools

4. You wrote rails new myapp but got an error: command not found: rails. What is the likely problem?

medium

A. The folder 'myapp' already exists

B. You typed the command correctly but your computer is off

C. You need to use ruby new myapp instead

D. Rails gem is not installed or not in your PATH

Solution

1. Step 1: Analyze the error message

   'command not found: rails' means the system cannot find the Rails command, usually because Rails is not installed or not set in PATH.

2. Step 2: Check options

   Rails gem is not installed or not in your PATH correctly identifies the cause. You typed the command correctly but your computer is off is unrelated to command errors. You need to use ruby new myapp instead is wrong syntax. The folder 'myapp' already exists would cause a different error.

3. Final Answer:

   Rails gem is not installed or not in your PATH -> Option D

4. Quick Check:

   Command not found means Rails missing = A [OK]

Hint: Command not found means Rails not installed or PATH missing [OK]

Common Mistakes:

• Assuming computer power off causes command errors
• Using wrong command syntax
• Confusing folder existence with command errors

5. Which of these best explains why Rails encourages 'convention over configuration'?

hard

A. It reduces the need to write extra setup code by following standard rules

B. It forces developers to configure every detail manually

C. It disables default settings to avoid confusion

D. It requires using only one database type

Solution

1. Step 1: Understand 'convention over configuration'

   This principle means Rails provides default ways to do things so developers write less setup code.

2. Step 2: Evaluate options

   It reduces the need to write extra setup code by following standard rules correctly explains this. Options A, C, and D contradict the idea or are unrelated.

3. Final Answer:

   It reduces the need to write extra setup code by following standard rules -> Option A

4. Quick Check:

   Convention means less config code = B [OK]

Hint: Convention means Rails sets defaults to save coding time [OK]

Common Mistakes:

• Thinking Rails forces manual config
• Believing defaults are disabled
• Assuming Rails limits database choices