Ruby on Rails — Request/respond flow

Ruby on Rails was created to make a developer’s life easier by not focusing too much on configuration but instead on conventions. Rails is not a language but a web application development framework. This framework allows developers, including those who did not create the code, the ability to follow along easily if changes need to be made to the application.

Let’s discuss the request/respond flow: The client side makes a request in the browser. The receiving server sends the request to the router and the router sees the request. The rails router will send the request to the correct controller. Controller interacts with the model; model interacts with the view and then the controller renders a view with the given data. To summaries, the sequence of events is as followed: Routes to Controller/action to Model to View.

So, why is it important to understand the request/respond flow? Well understanding the flow can help with the process of debugging your code. Becoming familiar with the patterns and sequence of events can greatly improve your debugging skills.