What is JHipster and what are its top alternatives?
Top Alternatives to JHipster
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 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 is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...
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. ...
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 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. ...
.NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications. ...
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
- Powerful and handy130
- Easy setup122
- Lots of "off the shelf" functionalities33
- Cloud Solid28
- Caches well22
- Many receipes around for obscure features20
- Integrations with most other Java frameworks18
- Spring ecosystem is great17
- Fast Performance With Microservices17
- Easy setup, Community Support, Solid for ERP apps12
- One-stop shop12
- Easy to parallelize11
- Easy setup, good for build erp systems, well documented10
- Powerful 3rd party libraries and frameworks10
- Easy setup, Git Integration9
- It's so easier to start a project on spring2
- Heavy weight18
- Annotation ceremony17
- Many config files needed10
- 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.
- Rapid development38
- Web framework29
- Open source24
- Clean architecture (Dependency Injection)6
- Clear what everything does, lots of options5
- Great documentation4
- 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?
- Rapid development610
- Open source453
- Great community390
- Easy to learn339
- Beautiful code205
- Great packages182
- Great libraries169
- Comes with auth and crud admin panel54
- Great documentation51
- Great for web48
- Great orm33
- Great for api28
- All included22
- Web Apps18
- Used by top startups14
- Easy setup11
- Convention over configuration8
- Allows for very rapid development with great libraries5
- The Django community5
- Its elegant and practical3
- Great MVC and templating engine3
- Easy Structure , useful inbuilt library2
- Full stack2
- Batteries included2
- Easy to use2
- Have not found anything that it can't do2
- Fast prototyping2
- Easy to develop end to end AI Models2
- Zero code burden to change databases1
- Full-Text Search1
- King of backend world1
- Very quick to get something up and running1
- Great peformance1
- Many libraries1
- Just the right level of abstraction1
- Python community1
- Underpowered templating24
- Underpowered ORM19
- Autoreload restarts whole server18
- URL dispatcher ignores HTTP method15
- Internal subcomponents coupling10
- Not nodejs7
- Configuration hell6
- Not as clean and nice documentation like Laravel3
- Not typed2
- Bloated admin panel included2
- Overwhelming folder structure2
- InEffective Multithreading1
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.
- Lightning-fast scaffolding121
- Great build process78
- Open source57
- Unit Testing8
related Yeoman posts
related CUBA Platform posts
- Great libraries1.1K
- Open source789
- Great for apis479
- Great community415
- Great for realtime apps386
- Great for command line utilities291
- Node Modules78
- Uber Simple65
- Allows us to reuse code in the frontend53
- Great modularity53
- Easy to start38
- Great for Data Streaming33
- Non blocking IO23
- Can be used as a proxy16
- High performance, open source, scalable15
- Non-blocking and modular14
- Easy and Fun13
- Same lang as AngularJS12
- Easy and powerful11
- Future of BackEnd10
- Cross platform8
- Mean Stack7
- Easy concurrency5
- Great for webapps5
- Easy to use and fast and goes well with JSONdb's4
- Fast, simple code and async4
- Its amazingly fast and scalable3
- Great speed3
- Fast development3
- Isomorphic coolness3
- Control everything3
- It's fast2
- Not Python2
- Blazing fast2
- One language, end-to-end2
- TypeScript Support2
- Easy to learn2
- Easy to use2
- Less boilerplate code2
- Sooper easy for the Backend connectivity2
- Great community2
- Scales, fast, simple, great community, npm, express2
- Performant and fast prototyping2
- Event Driven0
- Bound to a single CPU46
- New framework every day39
- Lots of terrible examples on the internet34
- Asynchronous programming is the worst28
- Dependency based on GitHub11
- Low computational power10
- Dependency hell10
- Can block whole server easily7
- Callback functions may not fire on expected sequence6
- Very very Slow6
- Breaking updates3
- Unneeded over complication3
- No standard approach1
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:
- Great mvc6
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...
I found Heroku to be a great option to get ExpressJS up and running with very little hustle. The free tier is great, but I'd recommend to set up a cronjob to visit your site every few minutes so that the server stays awake. Netlify was the option to host the front-end because doing the server side rendering on #Heroku would have taken a little more time than I'd like to. For the moment pre-rendering the app with prerender-spa-plugin is enough to help with #seo. Puppeteer was my choice over other options because it made it easier to scrape websites made on ASP.NET which is what I needed in this case. And Vue.js is my top choice at the moment because it's really beginner friendly and it has a lot of the features I like about Angular 2 and React. vuex is a must in most of the app I build.
- Clean architecture502
- Growing community361
- Composer friendly337
- Open source313
- The only framework to consider for php293
- Quickly develop189
- Dependency injection155
- Application architecture142
- Embraces good community packages129
- Write less, do more57
- Restful routing50
- Orm (eloquent)46
- Artisan scaffolding and migrations43
- Database migrations & seeds42
- Great documentation33
- Promotes elegant coding25
- Awsome, Powerfull, Fast and Rapid25
- Build Apps faster, easier and better24
- JSON friendly22
- Most easy for me21
- Eloquent ORM20
- Easy to learn, scalability20
- Modern PHP19
- Blade Template18
- Clean Documentation11
- Based on SOLID10
- Convention over Configuration10
- Easy to attach Middleware9
- Get going quickly straight out of the box. BYOKDM8
- Easy to use8
- Laravel + Cassandra = Killer Framework8
- Easy Request Validatin8
- Simplistic , easy and faster7
- Less dependencies7
- Its just wow7
- Super easy and powerful6
- Friendly API6
- Great customer support5
- Its beautiful to code in5
- Active Record4
- Fast and Clarify framework4
- The only "cons" is wrong! No static method just Facades4
- Easy views handling and great ORM3
- Minimum system requirements3
- Laravel Mix3
- Ease of use2
- Cashier with Braintree and Stripe2
- Laravel Spark2
- Laravel Passport2
- Laravel Nova2
- Laravel casher2
- Intuitive usage2
- Laravel Horizon and Telescope2
- Laravel Forge and Envoy2
- Touch heart artisan1
- Rapid development1
- Heart touch1
- Like heart beat1
- Laravel love live long1
- Too many dependency26
- Slower than the other two19
- A lot of static method calls for convenience15
- Too many include13
- Does not work well for file uploads in Shared Hosting4
- Too underrated3
- Not fast with MongoDB2
- Difficult to learn1
- Not using SOLID principles1
related Laravel posts
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.
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
I use Laravel because it's the most advances PHP framework out there, easy to maintain, easy to upgrade and most of all : easy to get a handle on, and to follow every new technology ! PhpStorm is our main software to code, as of simplicity and full range of tools for a modern application.
Google Analytics Analytics of course for a tailored analytics, Bulma as an innovative CSS framework, coupled with our Sass (Scss) pre-processor.
To deploy, we set up Buddy to easily send the updates on our nginx / Ubuntu server, where it will connect to our GitHub Git private repository, pull and do all the operations needed with Deployer .
CloudFlare ensure the rapidity of distribution of our content, and Let's Encrypt the https certificate that is more than necessary when we'll want to sell some products with our Stripe api calls.
Asana is here to let us list all the functionalities, possibilities and ideas we want to implement.