What is JHipster and what are its top alternatives?
Top Alternatives to JHipster
- 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. ...
- Yeoman
Yeoman is a robust and opinionated set of tools, libraries, and a workflow that can help developers quickly build beautiful, compelling web apps. It is comprised of yo - a scaffolding tool using our generator system, grunt - a task runner for your build process and bower for dependency management. ...
- CUBA Platform
It is a high-level open-source Java web framework for the rapid development of enterprise applications. The platform abstracts developers from underlying technologies so they can focus on the business tasks, whilst retaining full flexibility by providing unrestricted access to low-level code. Applications are developed in Java, with the user interface declared in XML. A rich set of features covers most typical project requirements and development tools reduce boilerplate code and facilitate truly rapid development. ...
- 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. ...
- 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. ...
JHipster alternatives & related posts
Spring Boot
- Powerful and handy136
- Easy setup128
- Java119
- Spring87
- Fast82
- Extensible43
- Lots of "off the shelf" functionalities34
- Cloud Solid29
- Caches well23
- Many receipes around for obscure features21
- Productive21
- Modular20
- Integrations with most other Java frameworks20
- Spring ecosystem is great19
- Auto-configuration18
- Fast Performance With Microservices18
- Community16
- Easy setup, Community Support, Solid for ERP apps14
- One-stop shop13
- Cross-platform12
- Easy to parallelize12
- Easy setup, good for build erp systems, well documented11
- Powerful 3rd party libraries and frameworks11
- Easy setup, Git Integration10
- It's so easier to start a project on spring3
- Kotlin3
- Heavy weight20
- Annotation ceremony17
- Many config files needed10
- Java8
- Reactive5
- Excellent tools for cloud hosting, since 5.x4
related Spring Boot posts






















We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.
To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas
To build #Webapps we decided to use Angular 2 with RxJS
#Devops - GitHub , Travis CI , Terraform , Docker , Serverless
Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.
Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.
- Groovy55
- Jvm39
- Rapid development38
- Gorm37
- Web framework29
- Open source24
- Plugins21
- Extensible17
- Easy16
- Dynamic14
- Clean architecture (Dependency Injection)6
- Gradle6
- Clear what everything does, lots of options5
- RAD4
- Great documentation4
- Agile4
- Android3
- Spring3
- Easy setup2
- Java web apps with steroid1
- Frequent breaking changes3
- Undocumented features2
related Grails posts
Some may wonder why did we choose Grails ? Really good question :) We spent quite some time to evaluate what framework to go with and the battle was between Play Scala and Grails ( Groovy ). We have enough experience with both and, to be honest, I absolutely in love with Scala; however, the tipping point for us was the potential speed of development. Grails allows much faster development pace than Play , and as of right now this is the most important parameter. We might convert later though. Also, worth mentioning, by default Grails comes with Gradle as a build tool, so why change?
Presently, a web-based ERP is developed in Groovy on Grails. Now the ERP is getting revamped with more functionalities. Is it advisable to continue with the same software and framework or try something new especially Node.js over ExpressJS?
- Rapid development641
- Open source473
- Great community406
- Easy to learn357
- Mvc266
- Beautiful code217
- Elegant212
- Free196
- Great packages194
- Great libraries182
- Restful71
- Powerful67
- Comes with auth and crud admin panel67
- Great documentation64
- Great for web61
- Python48
- Great orm38
- Great for api36
- All included27
- Web Apps22
- Fast22
- Used by top startups19
- Clean17
- Easy setup16
- Sexy16
- Convention over configuration13
- ORM12
- Allows for very rapid development with great libraries9
- The Django community9
- Great MVC and templating engine7
- King of backend world7
- Its elegant and practical7
- Mvt6
- Full stack6
- Fast prototyping6
- Have not found anything that it can't do6
- Cross-Platform6
- Batteries included5
- Very quick to get something up and running5
- Easy Structure , useful inbuilt library5
- Easy to develop end to end AI Models5
- Python community4
- Great peformance4
- Easy4
- Easy to use4
- Modular4
- Many libraries4
- Full-Text Search3
- Map3
- Zero code burden to change databases3
- Scaffold3
- Just the right level of abstraction3
- Easy to change database manager2
- Node js1
- Asdasd0
- Rails0
- Aaaa0
- Fastapi0
- Underpowered templating25
- Autoreload restarts whole server21
- Underpowered ORM20
- URL dispatcher ignores HTTP method15
- Internal subcomponents coupling10
- Not nodejs7
- Configuration hell7
- Admin7
- Not as clean and nice documentation like Laravel5
- Bloated admin panel included3
- Not typed3
- Python3
- Overwhelming folder structure2
- InEffective Multithreading2
related Django posts
Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.
Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.
For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.
However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.
All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.
Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?
- Lightning-fast scaffolding121
- Automation83
- Great build process78
- Open source57
- Yo49
- Unit Testing8
- Even harder to debug than Javascript1
related Yeoman posts
- Lots out of the box1
- Java1
- Component based1
related CUBA Platform posts
Node.js
- Npm1.4K
- Javascript1.3K
- Great libraries1.1K
- High-performance1K
- Open source798
- Great for apis484
- Asynchronous474
- Great community420
- Great for realtime apps390
- Great for command line utilities295
- Node Modules81
- Websockets80
- Uber Simple67
- Great modularity58
- Allows us to reuse code in the frontend56
- Easy to start41
- Great for Data Streaming35
- Realtime31
- Awesome27
- Non blocking IO24
- Can be used as a proxy17
- High performance, open source, scalable16
- Non-blocking and modular15
- Easy and Fun14
- Easy and powerful13
- Future of BackEnd12
- Same lang as AngularJS12
- Fullstack11
- Fast10
- Cross platform9
- Scalability9
- Simple8
- Mean Stack7
- Great for webapps6
- Easy concurrency6
- Fast, simple code and async5
- Friendly5
- Typescript5
- React5
- Easy to use and fast and goes well with JSONdb's4
- Scalable4
- Great speed4
- Control everything4
- Fast development4
- Its amazingly fast and scalable4
- Isomorphic coolness3
- It's fast3
- Easy to use3
- Easy to learn2
- Easy2
- Javascript22
- Great community2
- Not Python2
- Sooper easy for the Backend connectivity2
- TypeScript Support2
- Scales, fast, simple, great community, npm, express2
- One language, end-to-end2
- Less boilerplate code2
- Blazing fast2
- Performant and fast prototyping2
- Lovely1
- Event Driven1
- Npm i ape-updating1
- Bound to a single CPU46
- New framework every day42
- Lots of terrible examples on the internet37
- Asynchronous programming is the worst29
- Callback23
- Javascript18
- Dependency based on GitHub11
- Dependency hell10
- Low computational power10
- Can block whole server easily7
- Very very Slow7
- Callback functions may not fire on expected sequence6
- Unneeded over complication3
- Unstable3
- Breaking updates3
- No standard approach1
- Bad transitive dependency management1
- Can't read server session1
related Node.js posts
When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?
So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.
React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.
Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.











How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:
Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.
Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:
https://eng.uber.com/distributed-tracing/
(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)
Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark
ASP.NET
- Great mvc13
- Easy to learn5
- Not highly flexible for advance Developers1
- Entity framework is very slow1
related ASP.NET posts
Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.
This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!
But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?
I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.
Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...
Hi. We are planning to develop web, desktop, and mobile app for procurement, logistics, and contracts. Procure to Pay and Source to pay, spend management, supplier management, catalog management. ( similar to SAP Ariba, gap.com, coupa.com, ivalua.com vroozi.com, procurify.com
We got stuck when deciding which technology stack is good for the future. We look forward to your kind guidance that will help us.
We want to integrate with multiple databases with seamless bidirectional integration. What APIs and middleware available are best to achieve this? SAP HANA, Oracle, MySQL, MongoDB...
ASP.NET / Node.js / Laravel. ......?
Please guide us
- Clean architecture526
- Growing community379
- Composer friendly354
- Open source328
- The only framework to consider for php307
- Mvc208
- Quickly develop203
- Dependency injection161
- Application architecture150
- Embraces good community packages138
- Write less, do more67
- Orm (eloquent)62
- Restful routing60
- Database migrations & seeds51
- Artisan scaffolding and migrations50
- Great documentation36
- Awesome36
- Awsome, Powerfull, Fast and Rapid27
- Build Apps faster, easier and better25
- Promotes elegant coding25
- Eloquent ORM22
- Modern PHP22
- JSON friendly22
- Easy to learn, scalability22
- Most easy for me21
- Beautiful20
- Test-Driven20
- Blade Template20
- Security14
- Based on SOLID13
- Clean Documentation12
- Cool12
- Simple11
- Convention over Configuration11
- Easy to attach Middleware11
- Easy Request Validatin10
- Fast9
- Simpler9
- Easy to use9
- Laravel + Cassandra = Killer Framework8
- Its just wow8
- Friendly API8
- Get going quickly straight out of the box. BYOKDM8
- Simplistic , easy and faster7
- Super easy and powerful7
- Less dependencies7
- Great customer support6
- Its beautiful to code in6
- The only "cons" is wrong! No static method just Facades5
- Fast and Clarify framework5
- Active Record5
- Php75
- Speed5
- Easy5
- Composer4
- Laravel Mix4
- Minimum system requirements4
- Easy views handling and great ORM4
- Eloquent4
- Laragon4
- Laravel Spark3
- Ease of use3
- Cashier with Braintree and Stripe3
- Laravel Forge and Envoy3
- Laravel Horizon and Telescope3
- Laravel Nova3
- Laravel casher3
- Laravel Passport3
- Intuitive usage3
- Heart touch2
- Rapid development2
- Laravel love live long2
- Like heart beat2
- Touch heart artisan2
- Scout2
- Deployment1
- PHP44
- Too many dependency30
- Slower than the other two21
- A lot of static method calls for convenience17
- Too many include14
- Heavy11
- Bloated7
- Laravel6
- Confusing5
- Too underrated5
- Does not work well for file uploads in Shared Hosting4
- Not fast with MongoDB2
- Difficult to learn1
- Not using SOLID principles1
related Laravel posts
I need to build a web application plus android and IOS apps for an enterprise, like an e-commerce portal. It will have intensive use of MySQL to display thousands (40-50k) of live product information in an interactive table (searchable, filterable), live delivery tracking. It has to be secure, as it will handle information on customers, sales, inventory. Here is the technology stack: Backend: Laravel 7 Frondend: Vue.js, React or AngularJS?
Need help deciding technology stack. Thanks.
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