Get Advice Icon

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

JHipster
JHipster

29
19
+ 1
0
Laravel
Laravel

7.3K
4.5K
+ 1
2.8K
Add tool

JHipster vs Laravel: What are the differences?

What is JHipster? An Open Source application generator. It is a free and open-source application generator used to quickly develop modern web applications and Microservices using Spring Boot + Angular / React / Vue.

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.

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

JHipster and Laravel are both open source tools. It seems that Laravel with 53.4K GitHub stars and 16.4K forks on GitHub has more adoption than JHipster with 14.1K GitHub stars and 2.88K GitHub forks.

According to the StackShare community, Laravel has a broader approval, being mentioned in 831 company stacks & 777 developers stacks; compared to JHipster, which is listed in 5 company stacks and 5 developer stacks.

What is JHipster?

It is a free and open-source application generator used to quickly develop modern web applications and Microservices using Spring Boot + Angular / React / Vue.

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.
Get Advice Icon

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

Why do developers choose JHipster?
Why do developers choose Laravel?
    Be the first to leave a pro

    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 JHipster?
      What companies use Laravel?

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

      What tools integrate with JHipster?
      What tools integrate with Laravel?

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

      What are some alternatives to JHipster and Laravel?
      Spring Boot
      Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.
      Grails
      Grails is a framework used to build web applications with the Groovy programming language. The core framework is very extensible and there are numerous plugins available that provide easy integration of add-on features.
      Django
      Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
      Node.js
      Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.
      ASP.NET
      .NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications.
      See all alternatives
      Decisions about JHipster and Laravel
      Antonio Sanchez
      Antonio Sanchez
      CEO at Kokoen GmbH | 10 upvotes 69.9K views
      atKokoen GmbHKokoen GmbH
      ExpressJS
      ExpressJS
      Node.js
      Node.js
      JavaScript
      JavaScript
      MongoDB
      MongoDB
      Go
      Go
      MySQL
      MySQL
      Laravel
      Laravel
      PHP
      PHP

      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 480 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 27.9K views
      Debian
      Debian
      MySQL
      MySQL
      Laravel
      Laravel

      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 352 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 504 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 259 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
      Interest over time
      Reviews of JHipster and Laravel
      Review ofLaravelLaravel

      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 JHipster and Laravel
      Avatar of BrightMachine
      BrightMachine uses LaravelLaravel

      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.

      Avatar of Kent Steiner
      Kent Steiner uses LaravelLaravel

      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.

      Avatar of Nicholas Alexander
      Nicholas Alexander uses LaravelLaravel

      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.

      Avatar of Doug Bromley
      Doug Bromley uses LaravelLaravel

      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.

      Avatar of Jake Taylor
      Jake Taylor uses LaravelLaravel

      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.

      How much does JHipster cost?
      How much does Laravel cost?
      Pricing unavailable
      Pricing unavailable
      News about JHipster
      More news