Get Advice Icon

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

Laravel
Laravel

7.8K
4.8K
+ 1
2.9K
MEAN
MEAN

311
355
+ 1
590
Add tool

Laravel vs MEAN: What are the differences?

Developers describe Laravel as "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. On the other hand, MEAN is detailed as "A Simple, Scalable and Easy starting point for full stack javascript web development". MEAN (Mongo, Express, Angular, Node) is a boilerplate that provides a nice starting point for MongoDB, Node.js, Express, and AngularJS based applications. It is designed to give you a quick and organized way to start developing MEAN based web apps with useful modules like Mongoose and Passport pre-bundled and configured.

Laravel and MEAN belong to "Frameworks (Full Stack)" category of the tech stack.

"Clean architecture", "Growing community" and "Composer friendly" are the key factors why developers consider Laravel; whereas "Javascript", "Easy" and "Nosql" are the primary reasons why MEAN is favored.

Laravel and MEAN are both open source tools. It seems that Laravel with 53.4K GitHub stars and 16.4K forks on GitHub has more adoption than MEAN with 11.8K GitHub stars and 3.57K GitHub forks.

According to the StackShare community, Laravel has a broader approval, being mentioned in 831 company stacks & 773 developers stacks; compared to MEAN, which is listed in 37 company stacks and 24 developer stacks.

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 MEAN?

MEAN (Mongo, Express, Angular, Node) is a boilerplate that provides a nice starting point for MongoDB, Node.js, Express, and AngularJS based applications. It is designed to give you a quick and organized way to start developing MEAN based web apps with useful modules like Mongoose and Passport pre-bundled and configured.
Get Advice Icon

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

Why do developers choose Laravel?
Why do developers choose MEAN?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con

    Sign up to add, upvote and see more consMake informed product decisions

    What companies use Laravel?
    What companies use MEAN?

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

    What tools integrate with Laravel?
    What tools integrate with MEAN?

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

    What are some alternatives to Laravel and MEAN?
    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
    CakePHP 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.
    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.
    See all alternatives
    Decisions about Laravel and MEAN
    Antonio Sanchez
    Antonio Sanchez
    CEO at Kokoen GmbH | 12 upvotes 104.7K views
    atKokoen GmbHKokoen GmbH
    PHP
    PHP
    Laravel
    Laravel
    MySQL
    MySQL
    Go
    Go
    MongoDB
    MongoDB
    JavaScript
    JavaScript
    Node.js
    Node.js
    ExpressJS
    ExpressJS

    Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.

    Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.

    By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.

    Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.

    There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.

    We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.

    As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com

    See more
    Laravel
    Laravel

    I use Laravel because it has integrated unit testing that making TDD a breeze. Having a View (Blade engine) making me easier to work without too many efforts in front-end.

    I do recommend going into the root of programming once getting stable on any framework. Go beyond Symfony, go beyond PHP, go into the roots to the mother of programming; c++, c, smalltalk, erlang OTP. Understand the fundamental principle of abstraction.

    A framework is just a framework, it helps in getting feedback quickly; like practicing dancing in front of a mirror. Getting fundamentals right is the one true key in doing it right. Programming is not hard, but abstract-programming is extremely hard.

    See more
    David Block
    David Block
    Owner/Developer | 4 upvotes 485 views
    atNorth Creek Consulting, Inc.North Creek Consulting, Inc.
    Laravel
    Laravel

    I use Laravel because once a client asked me to use it, I recognized that as a solo programmer, I could go from idea to basic website in under an hour. Add one of the app builder templates and the basic design is done for me as well (I use AdminLTE). Lead management means a simple database and some basic workflow - that is where you should be spending your effort. Laravel is well-enough designed that you can plug in a few basic web pages, a simple set of object models, and some Controllers that hold your business logic - and then you iterate on the pages (the UI) and the business logic until your requirements are met. If you are a stickler or have corporate CSS standards, they can be implemented easily enough. And the community is huge and friendly.

    See more
    David Block
    David Block
    Owner/Developer | 8 upvotes 10.8K views
    atNorth Creek Consulting, Inc.North Creek Consulting, Inc.
    Laravel
    Laravel

    I use Laravel because once a client asked me to use it, I recognized that as a solo programmer, I could go from idea to basic website in under an hour. Add one of the app builder templates and the basic design is done for me as well (I use AdminLTE). Lead management means a simple database and some basic workflow - that is where you should be spending your effort. Laravel is well-enough designed that you can plug in a few basic web pages, a simple set of object models, and some Controllers that hold your business logic - and then you iterate on the pages (the UI) and the business logic until your requirements are met. If you are a stickler or have corporate CSS standards, they can be implemented easily enough. And the community is huge and friendly.

    See more
    Jason Martin
    Jason Martin
    Senior PHP Developer at Orange | 14 upvotes 43.5K views
    Laravel
    Laravel
    MySQL
    MySQL
    Debian
    Debian

    For your purposes, I recommend @Laravel, or even @Symfony or @Yii, or whatever. In your use case, a framework is 100% indicated, because it will cut your boilerplate in half or more, and you'll have a pre-fab organization for files, classes and so on. Personally, I am not a fan of Frameworks, because they tend to take over your project like cancer and trap you. But for an internal app to manage stuff, it's probably the best idea to use one (preferably one you like).

    When doing internal apps, your best bet is to stick the essentials and basics, try Laravel with MySQL on a nice Debian virtual machine. Can't go wrong.

    See more
    Tanner Naeher
    Tanner Naeher
    owner, designer, developer at Coyote6 GraphX | 3 upvotes 356 views
    Laravel
    Laravel

    If you are going to build from scratch use Laravel, because it is a little easier to learn than Symfony. They have a bunch of great videos to help you along the way. If you know Drupal 8 already, that is built on Symfony and you can harness the backend, but it is going to have a steeper learning curve. On the plus side you can take advantage of all its features. I wouldn't recommend building without a type of framework. Thousands of man hours have gone into those things for a reason. I started learning Symfony w/o Drupal but lost interest once I found out how much easier Laravel was. They both have their advantages and disadvantages, laravel actually uses part of symfony in its code. I like the blade template system better than twig is a big factor in deciding as well. They are both very similar, but blade is closer to native PHP which makes it a little easier to learn.

    See more
    Ahmet Ertem
    Ahmet Ertem
    Full Stack Developer | 5 upvotes 508 views
    Laravel
    Laravel

    I use Laravel because right now it's really hard to find someone using native PHP without a framework. Also learning a framework easier than native for newcomers. Also; I was not supporting frameworks before but after start developing a core with one I saw i can find many new people for the projects.

    See more
    Jigar Dhulla
    Jigar Dhulla
    Senior Application Developer at Endurance International Group | 2 upvotes 263 views
    Laravel
    Laravel

    I use Laravel because you don't have to re-invent the wheel when compared to core PHP. We can focus directly on business logic. And the little learning curve for Laravel is worth it. Can't really compare with Laravel with Symfony as I haven't worked with Symfony yet. My suggestion would be to pick one and stick to it. If at all you have to move to other, it should be easy. Last thing I would like to add is that there are more people around who knows Laravel compared to PHP, may be that's why I started with Laravel.

    See more
    Node.js
    Node.js
    Laravel
    Laravel
    PHP
    PHP
    React
    React
    Vue.js
    Vue.js

    I want to create a video sharing service like Youtube, which users can use to upload and watch videos. I prefer to use Vue.js for front-end. What do you suggest for the back-end? Node.js or Laravel ( PHP ) I need a good performance with high speed, and the most important thing is the ability to handle user's requests if the site's traffic increases. I want to create an algorithm that users who watch others videos earn points (randomly but in clear context) If you have anything else to improve, please let me know. For eg: If you prefer React to Vue.js. Thanks in advance

    See more
    Interest over time