Need advice about which tool to choose?Ask the StackShare community!

Laravel

18.5K
14.5K
+ 1
3.4K
Rails

14.5K
9.9K
+ 1
5.4K
Add tool

Laravel vs Rails: What are the differences?

What is Laravel? A PHP Framework For Web Artisans. Laravel is a web application framework with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Laravel attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

What is Rails? Web development that doesn't hurt. Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Laravel and Rails can be categorized as "Frameworks (Full Stack)" tools.

"Clean architecture", "Growing community" and "Composer friendly" are the key factors why developers consider Laravel; whereas "Rapid development", "Great gems" and "Great community" are the primary reasons why Rails is favored.

Laravel and Rails are both open source tools. Laravel with 53K GitHub stars and 16.2K forks on GitHub appears to be more popular than Rails with 43.4K GitHub stars and 17.5K GitHub forks.

According to the StackShare community, Rails has a broader approval, being mentioned in 2320 company stacks & 779 developers stacks; compared to Laravel, which is listed in 817 company stacks and 753 developer stacks.

Advice on Laravel and Rails
Needs advice
on
Laravel
Ignite UI
and
CakePHP

Hi, Which tool will you recommend:

I need to build a web application, oriented to small businesses, like a small ERP. It will have intensive use of Sql to access a PostgreSQL database. It has to be secure, as it will handle information on customers, sales, inventory.

If you think another tool will be better, please let that know.

Thanks a lot

See more
Replies (2)
Krunal Shah

Laravel and Postgres will be the better solutions you can add more like Redis for caching and React/Vue for the frontend.

See more
Recommends
Spring Boot

Check Spring, if security and reliability is needed along with Lots of Database , check Spring Data, spring web, spring security

See more
Needs advice
on
Node.js
and
Laravel

What will be better Laravel or Node.js to handle a logistics portal which displays thousands (20-50k) of delivery data information in an interactive table (searchable, filterable), live delivery tracking, basic user management, and report creation?

Data comes usually in CSV (manually uploaded or via API from courier companies). Live tracking uses checks tracking numbers on the courier page using API.

See more
Replies (1)
Francis Rodrigues
FullStack JavaScript Developer at PanelADM · | 4 upvotes · 32.3K views
Recommends
Node.js
Laravel

My question for you is: "Which one are you familiar with?" Following your needs, both could do it, but think about it. Now talking about Node.js, in my opinion, if you use JavaScript, there are lots of packages to support your entire project, including native ones for testing TDD and others for BDD. Also the best support on AWS (Amazon Web Services) and GCP (Google Cloud Platform).

See more
Leonardo Viada
Project manager and web developer at Revo Digital · | 4 upvotes · 13.9K views
Needs advice
on
Scala
Rails
and
Play
at

In the past few months, a project we're working on grew up quite fast. Since we're adding more and more features, I'm considering migrating my Express/TS REST API towards a more solid and more "enterprise-like" framework. Since I am experienced with TypeScript but not so much with Rails nor Play (Scala), I'd like to have some advice on which one could provide the best development experience, and most importantly, the smoothest paradigm transition from the JS/TS world. I've worked on some personal project with Rails, but I've found the Ruby language really distant from what the TypeScript ecosystem and syntax are, whereas on the opposite - during the brief tours I've taken in the past weeks - it's been a pleasure coding in Scala. Obviously, there are some key differences between the two languages - and the two frameworks consequently - but despite all the ROR automation and ease of use I don't despise at all Scala's pragmatic and great features such as static typing, pattern matching, and type inference. So... Please help me out with the choice! Regards

See more
Replies (4)
ALESSIO SALTARIN
Master IT Architect at IBM · | 5 upvotes · 11.7K views

If you are comfortable with TypeScript, why not evolve to a C# ecosystem? Asp.Net Core + Entity Framework is a mature and well supported technology. As far as I can see in the enterprise market, the most adopted choice is still Java. So, maybe you may have a look to SpringBoot - and ultimately Quarkus.

See more
Kevin Emery
QE Systems Engineer at Discovery, Inc. · | 5 upvotes · 11.3K views
Recommends
Rails

I don't have the Scala experience to compare the two, but I can say that Ruby is a wonderful language. For procedural programming where you don't need a lot of concurrent execution threads, it's superior to Node.JS in my opinion. All of the concepts from Typescript have equivalent syntax in Ruby, but there are fewer symbols (e.g. () => { ... }); ) and more keywords (eg 'do ... end'). It's a very flexible language and allows for a lot of different approaches to how it's written, so coding standards and careful organization is important. In the long run, however, you'll find it quicker to debug than Node.JS and just as powerful.

See more
malekmfs
at Meam Software Engineering Group · | 3 upvotes · 4.6K views
Recommends
Scala
Rails

This is advice regardless of your background and requirements. The Play framework has a terrible and complicated design, don't risk it. I even suggest Spring and Kotlin over it! You can use Scala for small services and Data Engineering stuff and benefit optimizations and threading of JVM. RoR, on the other hand, has a huge development speed, which I believe is a big advantage cause you can handle performance bottlenecks later. Also, Scala has another downside, which is featureful in terms of OO and FP paradigms, which makes anyone write code freely with any personal style and makes it a problem in a team, Hence a coding style has to be defined if there would be Scala development team.

See more
Hosam Aly
Senior Software Engineer · | 3 upvotes · 4.2K views
Recommends
Scala
Rails
Play

If software performance is your top priority, then Scala/Play is probably best. If developer productivity is your top priority, then Ruby on Rails is the best choice in my opinion.

The Rails framework is batteries-included. The framework takes care of many things by default so that you don't have to. Logging, security, etc. It's also well-integrated; for example, controllers understand models out of the box. I had a better experience with RoR than with Play.

On the other hand, Scala and the JVM are more performant in general, so they can scale to serve more requests per second on the same hardware.

If you're considering serverless functions, then Scala is probably a better choice because it would be faster to load, giving you better economics.

See more
View all (4)
Decisions about Laravel and Rails
Ing. Alvaro Rodríguez Scelza
Software Systems Engineer at Ripio · | 11 upvotes · 88.9K views

I was considering focusing on learning RoR and looking for a work that uses those techs.

After some investigation, I decided to stay with C# .NET:

  • It is more requested on job positions (7 to 1 in my personal searches average).

  • It's been around for longer.

  • it has better documentation and community.

  • One of Ruby advantages (its amazing community gems, that allows to quickly build parts of your systems by merely putting together third party components) gets quite complicated to use and maintain in huge applications, where building and reusing your own components may become a better approach.

  • Rail's front end support is starting to waver.

  • C# .NET code is far easier to understand, debug and maintain. Although certainly not easier to learn from scratch.

  • Though Rails has an excellent programming speed, C# tends to get the upper hand in long term projects.

I would avise to stick to rails when building small projects, and switching to C# for more long term ones.

Opinions are welcome!

See more

I am planning to develop project management system SAAS based. Can any one help me with selection of platforms from Django or Laravel and for database MongoDB or Firebase/Firestore or MySql? On front end I am going to use Quasar Framework (VueJS). Note : project will be Webapp, Mobile app and desktop app.

See more
Hampton Catlin
VP of Engineering at Rent The Runway · | 7 upvotes · 100K views

Starting a new company in 2020, with a whole new stack, is a really interesting opportunity for me to look back over the last 20 years of my career with web software and make the right decision for my company.

And, I went with the most radical decision– which is to ignore "sexy" / "hype" technologies almost entirely, and go back to a stack that I first used over 15 years ago.

For my purposes, we are building a video streaming platform, where I wanted rapid customer-facing feature development, high testability, simple scaling, and ease of hiring great, experienced talent. To be clear, our web platform is NOT responsible for handling the actual bits and bytes of the video itself, that's an entirely different stack. It simply needs to manage the business rules and the customers experience of the video content.

I reviewed a lot of different technologies, but none of them seemed to fit the bill as well as Rails did! The hype train had long left the station with Rails, and the community is a little more sparse than it was previously. And, to be honest, Ruby was the language that was easiest for developers, but I find that most languages out there have adopted many of it's innovations for ease of use – or at least corrected their own.

Even with all of that, Rails still seems like the best framework for developing web applications that are no more complex than they need to be. And that's key to me, because it's very easy to go use React and Redux and GraphQL and a whole host of AWS Lamba's to power my blog... but you simply don't actually NEED that.

There are two choices I made in our stack that were new for me personally, and very different than what I would have chosen even 5 years ago.

1) Postgres - I decided to switch from MySql to Postgres for this project. I wanted to use UUID's instead of numeric primary keys, and knew I'd have a couple places where better JSON/object support would be key. Mysql remains far more popular, but almost every developer I respect has switched and preferred Postgres with a strong passion. It's not "sexy" but it's considered "better".

2) Stimulus.js - This was definitely the biggest and wildest choice to make. Stimulus is a Javascript framework by my old friend Sam Stephenson (Prototype.js, rbenv, turbolinks) and DHH, and it is a sort of radical declaration that your Javascript in the browser can be both powerful and modern AND simple. It leans heavily on the belief that HTML-is-good and that data-* attributes are good. It focuses on the actions and interactions and not on the rendering aspects. It took me a while to wrap my head around, and I still have to remind myself, that server-side-HTML is how you solve many problems with this stack, and avoid trying to re-render things just in the browser. So far, I'm happy with this choice, but it is definitely a radical departure from the current trends.

See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Laravel
Pros of Rails
  • 504
    Clean architecture
  • 364
    Growing community
  • 339
    Composer friendly
  • 315
    Open source
  • 295
    The only framework to consider for php
  • 194
    Mvc
  • 189
    Quickly develop
  • 155
    Dependency injection
  • 143
    Application architecture
  • 129
    Embraces good community packages
  • 57
    Write less, do more
  • 52
    Restful routing
  • 47
    Orm (eloquent)
  • 43
    Artisan scaffolding and migrations
  • 42
    Database migrations & seeds
  • 35
    Awesome
  • 33
    Great documentation
  • 25
    Awsome, Powerfull, Fast and Rapid
  • 25
    Promotes elegant coding
  • 24
    Build Apps faster, easier and better
  • 22
    Easy to learn, scalability
  • 22
    JSON friendly
  • 21
    Most easy for me
  • 21
    Eloquent ORM
  • 19
    Modern PHP
  • 19
    Test-Driven
  • 18
    Beautiful
  • 18
    Blade Template
  • 13
    Security
  • 11
    Based on SOLID
  • 11
    Clean Documentation
  • 10
    Cool
  • 10
    Easy to attach Middleware
  • 10
    Simple
  • 10
    Convention over Configuration
  • 9
    Easy Request Validatin
  • 8
    Simpler
  • 8
    Get going quickly straight out of the box. BYOKDM
  • 8
    Its just wow
  • 8
    Fast
  • 8
    Laravel + Cassandra = Killer Framework
  • 8
    Easy to use
  • 7
    Super easy and powerful
  • 7
    Friendly API
  • 7
    Less dependencies
  • 7
    Simplistic , easy and faster
  • 6
    Great customer support
  • 6
    Its beautiful to code in
  • 5
    Php7
  • 5
    Active Record
  • 5
    Fast and Clarify framework
  • 5
    Easy
  • 5
    The only "cons" is wrong! No static method just Facades
  • 5
    Speed
  • 4
    Eloquent
  • 4
    Easy views handling and great ORM
  • 4
    Minimum system requirements
  • 4
    Laravel Mix
  • 4
    Composer
  • 4
    Laragon
  • 3
    Laravel Nova
  • 3
    Laravel casher
  • 3
    Laravel Spark
  • 3
    Intuitive usage
  • 3
    Ease of use
  • 3
    Cashier with Braintree and Stripe
  • 3
    Laravel Forge and Envoy
  • 3
    Laravel Horizon and Telescope
  • 3
    Laravel Passport
  • 2
    Heart touch
  • 2
    Like heart beat
  • 2
    Touch heart artisan
  • 2
    Scout
  • 2
    Rapid development
  • 2
    Laravel love live long
  • 847
    Rapid development
  • 648
    Great gems
  • 604
    Great community
  • 479
    Convention over configuration
  • 416
    Mvc
  • 349
    Great for web
  • 344
    Beautiful code
  • 311
    Open source
  • 270
    Great libraries
  • 260
    Active record
  • 105
    Elegant
  • 88
    Easy to learn
  • 86
    Easy Database Migrations
  • 78
    Makes you happy
  • 73
    Free
  • 62
    Great routing
  • 53
    Has everything you need to get the job done
  • 41
    Great Data Modeling
  • 38
    Beautiful
  • 38
    MVC - Easy to start on
  • 35
    Easy setup
  • 26
    Great caching
  • 25
    Ultra rapid development time
  • 22
    It's super easy
  • 17
    Great Resources
  • 16
    Easy to build mockups that work
  • 14
    Less Boilerplate
  • 7
    Developer Friendly
  • 7
    API Development
  • 6
    Great documentation
  • 5
    Easy REST API creation
  • 5
    Quick
  • 4
    Great language
  • 4
    Intuitive
  • 4
    Haml and sass
  • 4
    Easy to learn, use, improvise and update
  • 2
    It works
  • 2
    Jet packs come standard
  • 2
    Easy and fast
  • 2
    Legacy
  • 2
    Metaprogramming
  • 1
    Convention over configuration
  • 1
    Easy Testing
  • 1
    Cancan
  • 1
    It's intuitive

Sign up to add or upvote prosMake informed product decisions

Cons of Laravel
Cons of Rails
  • 40
    PHP
  • 27
    Too many dependency
  • 19
    Slower than the other two
  • 15
    A lot of static method calls for convenience
  • 13
    Too many include
  • 10
    Heavy
  • 7
    Bloated
  • 6
    Laravel
  • 5
    Confusing
  • 4
    Does not work well for file uploads in Shared Hosting
  • 3
    Too underrated
  • 2
    Not fast with MongoDB
  • 1
    Difficult to learn
  • 1
    Not using SOLID principles
  • 20
    Too much "magic" (hidden behavior)
  • 13
    Poor raw performance
  • 11
    Asset system is too primitive and outdated
  • 6
    Bloat in models
  • 6
    Heavy use of mixins
  • 3
    Very Very slow

Sign up to add or upvote consMake informed product decisions

What is Laravel?

It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

What is Rails?

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Need advice about which tool to choose?Ask the StackShare community!

What companies use Laravel?
What companies use Rails?
See which teams inside your own company are using Laravel or Rails.
Sign up for Private StackShareLearn More

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with Laravel?
What tools integrate with Rails?

Sign up to get full access to all the tool integrationsMake informed product decisions

Blog Posts

Jun 6 2019 at 5:11PM

AppSignal

+9
15
1077
+17
32
28385
+17
18
5594
What are some alternatives to Laravel and Rails?
Symfony
It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..
CodeIgniter
CodeIgniter is a proven, agile & open PHP web application framework with a small footprint. It is powering the next generation of web apps.
Django
Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
CakePHP
It makes building web applications simpler, faster, while requiring less code. A modern PHP 7 framework offering a flexible database access layer and a powerful scaffolding system.
WordPress
The core software is built by hundreds of community volunteers, and when you’re ready for more there are thousands of plugins and themes available to transform your site into almost anything you can imagine. Over 60 million people have chosen WordPress to power the place on the web they call “home” — we’d love you to join the family.
See all alternatives
Reviews of Laravel and Rails
Review of
Laravel

I moved from .NET and Rails to Laravel, and since then never thought to go back. I feel Laravel framework has the capability to overcome all modern frameworks.

At Soft Pyramid we are developing rich business applications using Laravel Framework, and never feel any limitation even for complex reporting.We have written REST apis, complex ERP solutions and found awsome in all areas.

How developers use Laravel and Rails
StackShare uses
Rails

The first live version of Leanstack was actually a WordPress site. There wasn’t a whole lot going on at first. We had static pages with static content that needed to be updated manually. Then came the concept of user-generated content and we made the switch to a full on Rails app in November of last year. Nick had a lot of experience with Rails so that made the decision pretty easy. But I had also played around with Rails previously and was comfortable working with it. I also knew I’d need to hire engineers with a lot more experience building web apps than I do, so I wanted to go with a language and framework other people would have experience with. Also, the sheer number of gems and tools available for Rails is pretty amazing (shout to RubyToolbox ).

I don’t see us ever having to move away from Rails really, but I could be wrong. Leanstack was built in Rails 3. For StackShare we decided to upgrade to Rails 4. Biggest issue with that has been caching. DHH decided to remove the standard page and action caching in favor of key-based caching (source)[http://edgeguides.rubyonrails.org/caching_with_rails.html#page-caching]. Probably a good thing from a framework-perspective. But pretty shitty to have to learn about that after testing out your new app and realizing nothing is cached anymore :( We’ll need to spend some more time implementing "Russian Doll Caching", but for now we’ve got a random mixture of fragment and action caching (usually one or the other) based on which pages are most popular.

Karma uses
Rails

We use Rails for webpages and projects, not for backend services. Actually if you click through our website, you won't notice it but you're clicking though, I think, seven or eight different Rails projects. We tie those all together with a front-end library that we wrote, which basically makes sure that you have a consistent experience over all these different Rails apps.

It's a gem, we call it Karmeleon. It's not a gem that we released. It's an internal gem. Basically what it does is it makes sure that we have a consistent layout across multiple Rails apps. Then we can share stuff like a menu bar or footer or that kind of stuff.

So if we start a new front end project it's always a Rails application. We pull in the Karmeleon gem with all our styling stuff and then basically the application is almost ready to be deployed. That would be an empty page, but you would still have top bar, footer, you have some custom components that you can immediately use. So it kind of bootstraps our entire project to be a front end project.

Instacart uses
Rails

Web has always been in Rails from the beginning, so we used Redis for caching our items, which we had, from the beginning. Rails is kind of what we were comfortable with, and we knew we wanted the front end to be really, really snappy, so we de-normalized all the item attributes into Redis, and that's how it got served out.

Tim Lucas uses
Rails

Rails 5 (beta 3) provided a nice structure for rendering responses, linking to front-end assets (compiled previously via Webpack), handling sessions w/ tailor made login links via an email button/token, background jobs, and creating an admin behind basic auth to allow managing of users and purchases.

Ngakkan Nyaagu uses
Rails

For this project rails was ideal due to new features introduced in Rails 5 that allowed us to build a lightweight "API only" project. Developer familiarity and the ability to rapidly iterate, as well as providing an accessible testing framework were additional factors.

bright machine uses
Laravel

The best PHP framework right now, intuitive and growing up quickly.

We use Laravel in the outer layer of our Clean Architecture codebases, whereby the domain model does not rely on the framework as a whole.

Kent Steiner uses
Laravel

See "PHP", I don't really choose to use it, but I can step in and operate in Laravel when necessary. Same goes for quite a few other PHP frameworks, including my own full-featured proprietary stack.

Nicholas Alexander uses
Laravel

An excellent PHP framework employing SOLID principles to rapidly develop web-site systems and connect them to databases. Custom development of admin screens for website management.

Doug Bromley uses
Laravel

A clean, easy to understand, well documented framework with excellent tools and a great community providing every imaginable extension to add functionality to your project.

Jake Taylor uses
Laravel

Laravel is the PHP framework we use. It speeds up development and simplifies a lot of PHP. Complicated at first but saves time once you're comfortable with it.