Alternatives to JHipster logo

Alternatives to JHipster

Spring Boot, Grails, Django, Yeoman, and CUBA Platform are the most popular alternatives and competitors to JHipster.
201
0

What is JHipster and what are its top alternatives?

JHipster is a popular open-source development platform that generates web applications using the Spring Boot backend and Angular front-end frameworks. It provides a powerful set of tools for creating and deploying modern web applications quickly. Key features include CRUD scaffolding, authentication and authorization mechanisms, automated testing, and Docker support. However, some limitations of JHipster include its steep learning curve for beginners and a complex project setup process.

  1. Spring Boot: Spring Boot is a popular Java-based framework that simplifies the development of standalone, production-grade Spring-based applications. Key features include a wide range of built-in dependencies, auto-configuration, and ease of deployment. Pros of Spring Boot compared to JHipster include a more lightweight and flexible approach, while cons may include the need for manual configuration in some cases.

  2. Micronaut: Micronaut is a modern, JVM-based framework designed for building modular, easily testable microservices and serverless applications. Key features include minimal memory consumption, fast startup times, and support for multiple programming languages. Pros of Micronaut compared to JHipster include improved performance and reduced memory usage, while cons may include a smaller community and fewer available plugins.

  3. Quarkus: Quarkus is a Kubernetes-native Java framework tailored for GraalVM and HotSpot, offering fast boot times and low memory usage. Key features include seamless integration with popular Java libraries and frameworks, reactive programming support, and cloud-native capabilities. Pros of Quarkus compared to JHipster include enhanced efficiency and reduced resource consumption, while cons may include a steeper learning curve for some developers.

  4. Vaadin: Vaadin is a Java web application framework that simplifies building modern web apps with Java. Key features include a rich set of components, client-server communication handled by the framework, and support for Java development. Pros of Vaadin compared to JHipster include a more user-friendly and intuitive UI development experience, while cons may include limited customization options compared to Angular or React.

  5. Grails: Grails is a framework built on top of Spring Boot and provides a Groovy-based approach to building web applications. Key features include convention over configuration, seamless integration with Spring and other Java libraries, and a productive development environment. Pros of Grails compared to JHipster include increased developer productivity and simplified configuration, while cons may include a smaller community and fewer available plugins.

  6. Play Framework: Play Framework is a Java and Scala web application framework that focuses on developer productivity and scalability. Key features include hot code reloading, a non-blocking I/O API, and asynchronous programming support. Pros of Play Framework compared to JHipster include enhanced performance and scalability, while cons may include a more specialized use case and potential learning curve for developers new to reactive programming.

  7. Dropwizard: Dropwizard is a high-performance Java framework for building RESTful web services. Key features include an integrated Jetty server, metrics and health checks, and seamless configuration management. Pros of Dropwizard compared to JHipster include improved performance and reduced overhead, while cons may include a narrower focus on RESTful services and less built-in functionality for frontend development.

  8. Spark Framework: Spark is a lightweight Java web framework that is ideal for creating REST APIs and microservices. Key features include simplicity, modularity, and a fast and expressive DSL. Pros of Spark Framework compared to JHipster include a minimalist approach and ease of use, while cons may include limited functionality for complex web applications and a smaller plugin ecosystem.

  9. Ratpack: Ratpack is a lightweight, asynchronous web framework for Java that focuses on high performance and developer productivity. Key features include composition over inheritance, reactive programming support, and a simple and flexible API. Pros of Ratpack compared to JHipster include increased performance and scalability, while cons may include a smaller community and potential learning curve for developers unfamiliar with reactive programming concepts.

  10. Dropwizard: Dropwizard is a high-performance Java framework for building RESTful web services. Key features include an integrated Jetty server, metrics and health checks, and seamless configuration management. Pros of Dropwizard compared to JHipster include improved performance and reduced overhead, while cons may include a narrower focus on RESTful services and less built-in functionality for frontend development.

Top Alternatives to JHipster

  • Spring Boot
    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

    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

    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...

  • Yeoman
    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
    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. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

  • Python
    Python

    Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best. ...

  • Node.js
    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. ...

JHipster alternatives & related posts

Spring Boot logo

Spring Boot

25.9K
23.6K
1K
Create Spring-powered, production-grade applications and services with absolute minimum fuss
25.9K
23.6K
+ 1
1K
PROS OF SPRING BOOT
  • 149
    Powerful and handy
  • 134
    Easy setup
  • 128
    Java
  • 90
    Spring
  • 85
    Fast
  • 46
    Extensible
  • 37
    Lots of "off the shelf" functionalities
  • 32
    Cloud Solid
  • 26
    Caches well
  • 24
    Productive
  • 24
    Many receipes around for obscure features
  • 23
    Modular
  • 23
    Integrations with most other Java frameworks
  • 22
    Spring ecosystem is great
  • 21
    Auto-configuration
  • 21
    Fast Performance With Microservices
  • 18
    Community
  • 17
    Easy setup, Community Support, Solid for ERP apps
  • 15
    One-stop shop
  • 14
    Easy to parallelize
  • 14
    Cross-platform
  • 13
    Easy setup, good for build erp systems, well documented
  • 13
    Powerful 3rd party libraries and frameworks
  • 12
    Easy setup, Git Integration
  • 5
    It's so easier to start a project on spring
  • 4
    Kotlin
  • 1
    Microservice and Reactive Programming
  • 1
    The ability to integrate with the open source ecosystem
CONS OF SPRING BOOT
  • 23
    Heavy weight
  • 18
    Annotation ceremony
  • 13
    Java
  • 11
    Many config files needed
  • 5
    Reactive
  • 4
    Excellent tools for cloud hosting, since 5.x
  • 1
    Java 😒😒

related Spring Boot posts

Praveen Mooli
Engineering Manager at Taylor and Francis · | 19 upvotes · 4M views

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

See more

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.

See more
Grails logo

Grails

386
373
333
An Open Source, full stack, web application framework for the JVM
386
373
+ 1
333
PROS OF GRAILS
  • 56
    Groovy
  • 40
    Jvm
  • 38
    Rapid development
  • 37
    Gorm
  • 30
    Web framework
  • 25
    Open source
  • 21
    Plugins
  • 17
    Extensible
  • 17
    Easy
  • 14
    Dynamic
  • 6
    Clean architecture (Dependency Injection)
  • 6
    Gradle
  • 5
    Clear what everything does, lots of options
  • 4
    RAD
  • 4
    Agile
  • 4
    Great documentation
  • 3
    Android
  • 3
    Spring
  • 2
    Easy setup
  • 1
    Java web apps with steroid
CONS OF GRAILS
  • 3
    Frequent breaking changes
  • 2
    Undocumented features

related Grails posts

Alex A

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?

See more

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?

See more
Django logo

Django

37.6K
34K
4.2K
The Web framework for perfectionists with deadlines
37.6K
34K
+ 1
4.2K
PROS OF DJANGO
  • 673
    Rapid development
  • 487
    Open source
  • 425
    Great community
  • 379
    Easy to learn
  • 277
    Mvc
  • 232
    Beautiful code
  • 223
    Elegant
  • 207
    Free
  • 203
    Great packages
  • 194
    Great libraries
  • 80
    Comes with auth and crud admin panel
  • 79
    Restful
  • 78
    Powerful
  • 76
    Great documentation
  • 72
    Great for web
  • 57
    Python
  • 43
    Great orm
  • 41
    Great for api
  • 32
    All included
  • 29
    Fast
  • 25
    Web Apps
  • 23
    Clean
  • 23
    Easy setup
  • 21
    Used by top startups
  • 19
    Sexy
  • 19
    ORM
  • 15
    The Django community
  • 14
    Allows for very rapid development with great libraries
  • 14
    Convention over configuration
  • 11
    King of backend world
  • 10
    Full stack
  • 10
    Great MVC and templating engine
  • 8
    Mvt
  • 8
    Fast prototyping
  • 7
    Its elegant and practical
  • 7
    Easy to develop end to end AI Models
  • 7
    Batteries included
  • 6
    Cross-Platform
  • 6
    Very quick to get something up and running
  • 6
    Have not found anything that it can't do
  • 5
    Zero code burden to change databases
  • 5
    Great peformance
  • 5
    Python community
  • 5
    Easy Structure , useful inbuilt library
  • 4
    Easy to use
  • 4
    Map
  • 4
    Easy to change database manager
  • 4
    Full-Text Search
  • 4
    Just the right level of abstraction
  • 4
    Many libraries
  • 4
    Modular
  • 4
    Easy
  • 3
    Scaffold
  • 1
    Node js
  • 1
    Built in common security
  • 1
    Great default admin panel
  • 1
    Scalable
  • 1
    Gigante ta
  • 1
    Cons
  • 1
    Fastapi
  • 0
    Rails
CONS OF DJANGO
  • 26
    Underpowered templating
  • 22
    Autoreload restarts whole server
  • 22
    Underpowered ORM
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
  • 8
    Not nodejs
  • 8
    Configuration hell
  • 7
    Admin
  • 5
    Not as clean and nice documentation like Laravel
  • 4
    Python
  • 3
    Not typed
  • 3
    Bloated admin panel included
  • 2
    Overwhelming folder structure
  • 2
    InEffective Multithreading
  • 1
    Not type safe

related Django posts

Dmitry Mukhin
Engineer at Uploadcare · | 25 upvotes · 2.6M views

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.

See more

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?

See more
Yeoman logo

Yeoman

1.7K
1.3K
396
A set of tools for automating development workflow
1.7K
1.3K
+ 1
396
PROS OF YEOMAN
  • 121
    Lightning-fast scaffolding
  • 83
    Automation
  • 78
    Great build process
  • 57
    Open source
  • 49
    Yo
  • 8
    Unit Testing
CONS OF YEOMAN
  • 1
    Even harder to debug than Javascript

related Yeoman posts

CUBA Platform logo

CUBA Platform

9
23
3
A full stack Java framework and components for business applications
9
23
+ 1
3
PROS OF CUBA PLATFORM
  • 1
    Lots out of the box
  • 1
    Java
  • 1
    Component based
CONS OF CUBA PLATFORM
    Be the first to leave a con

    related CUBA Platform posts

    JavaScript logo

    JavaScript

    360K
    273.8K
    8.1K
    Lightweight, interpreted, object-oriented language with first-class functions
    360K
    273.8K
    + 1
    8.1K
    PROS OF JAVASCRIPT
    • 1.7K
      Can be used on frontend/backend
    • 1.5K
      It's everywhere
    • 1.2K
      Lots of great frameworks
    • 898
      Fast
    • 745
      Light weight
    • 425
      Flexible
    • 392
      You can't get a device today that doesn't run js
    • 286
      Non-blocking i/o
    • 237
      Ubiquitousness
    • 191
      Expressive
    • 55
      Extended functionality to web pages
    • 49
      Relatively easy language
    • 46
      Executed on the client side
    • 30
      Relatively fast to the end user
    • 25
      Pure Javascript
    • 21
      Functional programming
    • 15
      Async
    • 13
      Full-stack
    • 12
      Setup is easy
    • 12
      Future Language of The Web
    • 12
      Its everywhere
    • 11
      Because I love functions
    • 11
      JavaScript is the New PHP
    • 10
      Like it or not, JS is part of the web standard
    • 9
      Expansive community
    • 9
      Everyone use it
    • 9
      Can be used in backend, frontend and DB
    • 9
      Easy
    • 8
      Most Popular Language in the World
    • 8
      Powerful
    • 8
      Can be used both as frontend and backend as well
    • 8
      For the good parts
    • 8
      No need to use PHP
    • 8
      Easy to hire developers
    • 7
      Agile, packages simple to use
    • 7
      Love-hate relationship
    • 7
      Photoshop has 3 JS runtimes built in
    • 7
      Evolution of C
    • 7
      It's fun
    • 7
      Hard not to use
    • 7
      Versitile
    • 7
      Its fun and fast
    • 7
      Nice
    • 7
      Popularized Class-Less Architecture & Lambdas
    • 7
      Supports lambdas and closures
    • 6
      It let's me use Babel & Typescript
    • 6
      Can be used on frontend/backend/Mobile/create PRO Ui
    • 6
      1.6K Can be used on frontend/backend
    • 6
      Client side JS uses the visitors CPU to save Server Res
    • 6
      Easy to make something
    • 5
      Clojurescript
    • 5
      Promise relationship
    • 5
      Stockholm Syndrome
    • 5
      Function expressions are useful for callbacks
    • 5
      Scope manipulation
    • 5
      Everywhere
    • 5
      Client processing
    • 5
      What to add
    • 4
      Because it is so simple and lightweight
    • 4
      Only Programming language on browser
    • 1
      Test
    • 1
      Hard to learn
    • 1
      Test2
    • 1
      Not the best
    • 1
      Easy to understand
    • 1
      Subskill #4
    • 1
      Easy to learn
    • 0
      Hard 彤
    CONS OF JAVASCRIPT
    • 22
      A constant moving target, too much churn
    • 20
      Horribly inconsistent
    • 15
      Javascript is the New PHP
    • 9
      No ability to monitor memory utilitization
    • 8
      Shows Zero output in case of ANY error
    • 7
      Thinks strange results are better than errors
    • 6
      Can be ugly
    • 3
      No GitHub
    • 2
      Slow
    • 0
      HORRIBLE DOCUMENTS, faulty code, repo has bugs

    related JavaScript posts

    Zach Holman

    Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

    But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

    But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

    Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

    See more
    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 12.6M views

    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

    See more
    Python logo

    Python

    244.5K
    199.6K
    6.9K
    A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
    244.5K
    199.6K
    + 1
    6.9K
    PROS OF PYTHON
    • 1.2K
      Great libraries
    • 962
      Readable code
    • 847
      Beautiful code
    • 788
      Rapid development
    • 690
      Large community
    • 438
      Open source
    • 393
      Elegant
    • 282
      Great community
    • 272
      Object oriented
    • 220
      Dynamic typing
    • 77
      Great standard library
    • 60
      Very fast
    • 55
      Functional programming
    • 49
      Easy to learn
    • 45
      Scientific computing
    • 35
      Great documentation
    • 29
      Productivity
    • 28
      Easy to read
    • 28
      Matlab alternative
    • 24
      Simple is better than complex
    • 20
      It's the way I think
    • 19
      Imperative
    • 18
      Free
    • 18
      Very programmer and non-programmer friendly
    • 17
      Powerfull language
    • 17
      Machine learning support
    • 16
      Fast and simple
    • 14
      Scripting
    • 12
      Explicit is better than implicit
    • 11
      Ease of development
    • 10
      Clear and easy and powerfull
    • 9
      Unlimited power
    • 8
      It's lean and fun to code
    • 8
      Import antigravity
    • 7
      Print "life is short, use python"
    • 7
      Python has great libraries for data processing
    • 6
      Although practicality beats purity
    • 6
      Now is better than never
    • 6
      Great for tooling
    • 6
      Readability counts
    • 6
      Rapid Prototyping
    • 6
      I love snakes
    • 6
      Flat is better than nested
    • 6
      Fast coding and good for competitions
    • 6
      There should be one-- and preferably only one --obvious
    • 6
      High Documented language
    • 5
      Great for analytics
    • 5
      Lists, tuples, dictionaries
    • 4
      Easy to learn and use
    • 4
      Simple and easy to learn
    • 4
      Easy to setup and run smooth
    • 4
      Web scraping
    • 4
      CG industry needs
    • 4
      Socially engaged community
    • 4
      Complex is better than complicated
    • 4
      Multiple Inheritence
    • 4
      Beautiful is better than ugly
    • 4
      Plotting
    • 3
      Many types of collections
    • 3
      Flexible and easy
    • 3
      It is Very easy , simple and will you be love programmi
    • 3
      If the implementation is hard to explain, it's a bad id
    • 3
      Special cases aren't special enough to break the rules
    • 3
      Pip install everything
    • 3
      List comprehensions
    • 3
      No cruft
    • 3
      Generators
    • 3
      Import this
    • 3
      If the implementation is easy to explain, it may be a g
    • 2
      Can understand easily who are new to programming
    • 2
      Batteries included
    • 2
      Securit
    • 2
      Good for hacking
    • 2
      Better outcome
    • 2
      Only one way to do it
    • 2
      Because of Netflix
    • 2
      A-to-Z
    • 2
      Should START with this but not STICK with This
    • 2
      Powerful language for AI
    • 1
      Automation friendly
    • 1
      Sexy af
    • 1
      Slow
    • 1
      Procedural programming
    • 0
      Ni
    • 0
      Powerful
    • 0
      Keep it simple
    CONS OF PYTHON
    • 53
      Still divided between python 2 and python 3
    • 28
      Performance impact
    • 26
      Poor syntax for anonymous functions
    • 22
      GIL
    • 19
      Package management is a mess
    • 14
      Too imperative-oriented
    • 12
      Hard to understand
    • 12
      Dynamic typing
    • 12
      Very slow
    • 8
      Indentations matter a lot
    • 8
      Not everything is expression
    • 7
      Incredibly slow
    • 7
      Explicit self parameter in methods
    • 6
      Requires C functions for dynamic modules
    • 6
      Poor DSL capabilities
    • 6
      No anonymous functions
    • 5
      Fake object-oriented programming
    • 5
      Threading
    • 5
      The "lisp style" whitespaces
    • 5
      Official documentation is unclear.
    • 5
      Hard to obfuscate
    • 5
      Circular import
    • 4
      Lack of Syntax Sugar leads to "the pyramid of doom"
    • 4
      The benevolent-dictator-for-life quit
    • 4
      Not suitable for autocomplete
    • 2
      Meta classes
    • 1
      Training wheels (forced indentation)

    related Python posts

    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 12.6M views

    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

    See more
    Nick Parsons
    Building cool things on the internet 🛠️ at Stream · | 35 upvotes · 4.3M views

    Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.

    We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. With ES6 and Node.js v10.x.x, it’s become a very capable language. Async/Await is powerful and easy to use (Async/Await vs Promises). Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks)

    We’re using JavaScript for everything – both front and backend. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app.

    Sure... there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js); however, without writing completely in JavaScript, we would not have seen the results we did.

    #FrameworksFullStack #Languages

    See more
    Node.js logo

    Node.js

    188.3K
    159.9K
    8.5K
    A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
    188.3K
    159.9K
    + 1
    8.5K
    PROS OF NODE.JS
    • 1.4K
      Npm
    • 1.3K
      Javascript
    • 1.1K
      Great libraries
    • 1K
      High-performance
    • 805
      Open source
    • 486
      Great for apis
    • 477
      Asynchronous
    • 423
      Great community
    • 390
      Great for realtime apps
    • 296
      Great for command line utilities
    • 84
      Websockets
    • 83
      Node Modules
    • 69
      Uber Simple
    • 59
      Great modularity
    • 58
      Allows us to reuse code in the frontend
    • 42
      Easy to start
    • 35
      Great for Data Streaming
    • 32
      Realtime
    • 28
      Awesome
    • 25
      Non blocking IO
    • 18
      Can be used as a proxy
    • 17
      High performance, open source, scalable
    • 16
      Non-blocking and modular
    • 15
      Easy and Fun
    • 14
      Easy and powerful
    • 13
      Future of BackEnd
    • 13
      Same lang as AngularJS
    • 12
      Fullstack
    • 11
      Fast
    • 10
      Scalability
    • 10
      Cross platform
    • 9
      Simple
    • 8
      Mean Stack
    • 7
      Great for webapps
    • 7
      Easy concurrency
    • 6
      Typescript
    • 6
      Fast, simple code and async
    • 6
      React
    • 6
      Friendly
    • 5
      Control everything
    • 5
      Its amazingly fast and scalable
    • 5
      Easy to use and fast and goes well with JSONdb's
    • 5
      Scalable
    • 5
      Great speed
    • 5
      Fast development
    • 4
      It's fast
    • 4
      Easy to use
    • 4
      Isomorphic coolness
    • 3
      Great community
    • 3
      Not Python
    • 3
      Sooper easy for the Backend connectivity
    • 3
      TypeScript Support
    • 3
      Blazing fast
    • 3
      Performant and fast prototyping
    • 3
      Easy to learn
    • 3
      Easy
    • 3
      Scales, fast, simple, great community, npm, express
    • 3
      One language, end-to-end
    • 3
      Less boilerplate code
    • 2
      Npm i ape-updating
    • 2
      Event Driven
    • 2
      Lovely
    • 1
      Creat for apis
    • 0
      Node
    CONS OF NODE.JS
    • 46
      Bound to a single CPU
    • 45
      New framework every day
    • 40
      Lots of terrible examples on the internet
    • 33
      Asynchronous programming is the worst
    • 24
      Callback
    • 19
      Javascript
    • 11
      Dependency hell
    • 11
      Dependency based on GitHub
    • 10
      Low computational power
    • 7
      Very very Slow
    • 7
      Can block whole server easily
    • 7
      Callback functions may not fire on expected sequence
    • 4
      Breaking updates
    • 4
      Unstable
    • 3
      Unneeded over complication
    • 3
      No standard approach
    • 1
      Bad transitive dependency management
    • 1
      Can't read server session

    related Node.js posts

    Shared insights
    on
    Node.jsNode.jsGraphQLGraphQLMongoDBMongoDB

    I just finished the very first version of my new hobby project: #MovieGeeks. It is a minimalist online movie catalog for you to save the movies you want to see and for rating the movies you already saw. This is just the beginning as I am planning to add more features on the lines of sharing and discovery

    For the #BackEnd I decided to use Node.js , GraphQL and MongoDB:

    1. Node.js has a huge community so it will always be a safe choice in terms of libraries and finding solutions to problems you may have

    2. GraphQL because I needed to improve my skills with it and because I was never comfortable with the usual REST approach. I believe GraphQL is a better option as it feels more natural to write apis, it improves the development velocity, by definition it fixes the over-fetching and under-fetching problem that is so common on REST apis, and on top of that, the community is getting bigger and bigger.

    3. MongoDB was my choice for the database as I already have a lot of experience working on it and because, despite of some bad reputation it has acquired in the last months, I still believe it is a powerful database for at least a very long list of use cases such as the one I needed for my website

    See more
    Nick Rockwell
    SVP, Engineering at Fastly · | 46 upvotes · 4.1M views

    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.

    See more