New Blog Post: Ruby on Rails - A developer's perspective#420
Open
mthomas-scottlogic wants to merge 18 commits into
Open
New Blog Post: Ruby on Rails - A developer's perspective#420mthomas-scottlogic wants to merge 18 commits into
mthomas-scottlogic wants to merge 18 commits into
Conversation
Comment on lines
+97
to
+98
| Features such as | ||
| `dependent: :destroy` stood out to me, as they allow cascading behaviour to be expressed clearly in code without introducing additional complexity at the database layer. |
Contributor
There was a problem hiding this comment.
I'm bit confused what dependent: :destroy here. Can you you include it to Product class so it ties everything listed under this section together.
Contributor
Author
There was a problem hiding this comment.
I added that into sample code and added more details on its purpose to avoid confusion.
Comment on lines
+112
to
+122
| ### Comparing Spring and Rails | ||
|
|
||
| Working with Ruby on Rails felt both familiar and disorienting in equal measure. The high-level architectural concepts — MVC, layered responsibilities, and REST-centric design — are recognisable, but the way Rails guides you towards those outcomes is markedly different. | ||
|
|
||
| The most immediate difference was how much Rails removes up-front decision-making. As a Spring developer, I’m used to explicitly defining configuration, wiring dependencies, and making architectural intent visible through annotations and structure. Rails, by contrast, leans heavily into convention over configuration. At first, this felt uncomfortable — almost like important details were being hidden. Over time, though, it became clear that Rails isn’t removing complexity so much as delaying it until it’s actually needed. | ||
|
|
||
| Active Record was another notable shift. Compared to Hibernate/JPA, it’s far more opinionated and is tightly integrated into the framework. It’s designed to be simple and intuitive for common use cases, but it can feel restrictive when you need to do something unconventional. In contrast, Hibernate/JPA offers more flexibility at the cost of simplicity. | ||
|
|
||
| Rails’ ORM significantly reduced boilerplate and allowed features to be delivered quickly with minimal ceremony. The trade-off is that you need to be disciplined in understanding what the framework is doing on your behalf — especially as data access patterns become more complex. | ||
|
|
||
| The framework, tooling, and ecosystem are optimised to get something working end to end quickly. Compared to Spring Boot, where robustness and explicit configuration reinforce enterprise safety, Rails prioritises momentum. For early-stage development or well-bounded domains, this feels like a genuine advantage rather than a shortcut. |
Contributor
There was a problem hiding this comment.
I feel like some of the things mentioned here are repeated elsewhere on the article. Ignore this if it doesn't make sense
Contributor
Author
There was a problem hiding this comment.
You are right, I have improved it, so it doesn't feel too repetitive.
smendis-scottlogic
approved these changes
May 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please add a direct link to your post here:
https://mthomas-scottlogic.github.io/blog/2026/05/18/ruby-on-rails-a-developers-perspective.html
Have you (please tick each box to show completion):
npm installfollowed bynpx mdspell "**/{FILE_NAME}.md" --en-gb -a -n -x -tif that's your thing)Posts are reviewed / approved by your Regional Tech Lead.