Appreciating the MVC Architecture
Working on updating my final Flatiron project this week ( generating a new resource on the backend with corresponding action’s on the front), has led me to appreciate the sleekness of Rails’ design and how much it facilitates productivity, particularly in regards to the MVC architecture and the separation of concerns principle. It is a beautiful thing.
Though no V in the MVC was dealt with due to React being run on the frontend, I found myself appreciating the straightforward approach of the logic of the MVC in constructing the routes for UI access. An excellent resource for understand the MVC architecture in ActiveRecord can be found here
The separation of concerns is truly as it named, in the sense that it really allows to tidily deal with the conceptual processes. In other words I find that it is a great concept to help organize my thinking. To know that all validations, authentications, protections etc. are to dealt with in one section (model) and that all logic to do with my routes for UI interface is in another (controller) really does make it so much easier to approach a change I wish to implement.