Alternatives to AngularJS logo

Alternatives to AngularJS

JavaScript, Angular 2, React, Node.js, and jQuery are the most popular alternatives and competitors to AngularJS.
42.3K
30K
+ 1
5.3K

What is AngularJS and what are its top alternatives?

AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML鈥檚 syntax to express your application鈥檚 components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding.
AngularJS is a tool in the Javascript MVC Frameworks category of a tech stack.
AngularJS is an open source tool with 59.6K GitHub stars and 28.5K GitHub forks. Here鈥檚 a link to AngularJS's open source repository on GitHub

Top Alternatives to AngularJS

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

  • Angular 2

    Angular 2

    It is a TypeScript-based open-source web application framework. It is a development platform for building mobile and desktop web applications. ...

  • React

    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

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

  • jQuery

    jQuery

    jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML. ...

  • PHP

    PHP

    Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world. ...

  • Angular CLI

    Angular CLI

    A command-line interface tool that you use to initialize, develop, scaffold, and maintain Angular applications. You can use the tool directly in a command shell, or indirectly through an interactive UI such as Angular Console. ...

  • Vue.js

    Vue.js

    It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API. ...

AngularJS alternatives & related posts

JavaScript logo

JavaScript

196.1K
150.5K
7.7K
Lightweight, interpreted, object-oriented language with first-class functions
196.1K
150.5K
+ 1
7.7K
PROS OF JAVASCRIPT
  • 1.6K
    Can be used on frontend/backend
  • 1.5K
    It's everywhere
  • 1.1K
    Lots of great frameworks
  • 885
    Fast
  • 734
    Light weight
  • 412
    Flexible
  • 379
    You can't get a device today that doesn't run js
  • 281
    Non-blocking i/o
  • 231
    Ubiquitousness
  • 186
    Expressive
  • 49
    Extended functionality to web pages
  • 42
    Relatively easy language
  • 40
    Executed on the client side
  • 24
    Relatively fast to the end user
  • 20
    Pure Javascript
  • 15
    Functional programming
  • 9
    Async
  • 7
    Setup is easy
  • 6
    Because I love functions
  • 6
    JavaScript is the New PHP
  • 6
    Full-stack
  • 5
    Future Language of The Web
  • 5
    Expansive community
  • 5
    Its everywhere
  • 5
    Can be used in backend, frontend and DB
  • 5
    Like it or not, JS is part of the web standard
  • 4
    Everyone use it
  • 4
    Agile, packages simple to use
  • 4
    Supports lambdas and closures
  • 4
    Popularized Class-Less Architecture & Lambdas
  • 4
    Evolution of C
  • 4
    For the good parts
  • 4
    Easy to hire developers
  • 4
    Love-hate relationship
  • 3
    Because it is so simple and lightweight
  • 3
    Only Programming language on browser
  • 3
    Nice
  • 3
    Easy to make something
  • 3
    Promise relationship
  • 3
    Scope manipulation
  • 3
    Hard not to use
  • 3
    Client processing
  • 3
    It's fun
  • 3
    Everywhere
  • 3
    Function expressions are useful for callbacks
  • 3
    Can be used on frontend/backend/Mobile/create PRO Ui
  • 3
    What to add
  • 3
    1.6K Can be used on frontend/backend
  • 3
    Can be used both as frontend and backend as well
  • 3
    Easy
  • 3
    Clojurescript
  • 3
    Stockholm Syndrome
  • 3
    It let's me use Babel & Typescript
  • 3
    Client side JS uses the visitors CPU to save Server Res
  • 3
    Its fun and fast
  • 3
    Powerful
  • 3
    Most Popular Language in the World
  • 3
    Versitile
  • 3
    No need to use PHP
  • 3
    Photoshop has 3 JS runtimes built in
  • 1
    Acoperi葯ul 0757604335
  • 1
    JavaScript j.s
CONS OF JAVASCRIPT
  • 21
    A constant moving target, too much churn
  • 20
    Horribly inconsistent
  • 14
    Javascript is the New PHP
  • 8
    No ability to monitor memory utilitization
  • 6
    Shows Zero output in case of ANY error
  • 5
    Can be ugly
  • 4
    Thinks strange results are better than errors
  • 2
    No GitHub
  • 1
    Slow

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 | 38 upvotes 路 3.8M 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
Angular 2 logo

Angular 2

4.5K
3.5K
417
A platform for building mobile and desktop web applications
4.5K
3.5K
+ 1
417
PROS OF ANGULAR 2
  • 95
    It's a powerful framework
  • 47
    Straight-forward architecture
  • 40
    TypeScript
  • 39
    Great UI and Business Logic separation
  • 37
    Powerful, maintainable, fast
  • 34
    Amazing CLI
  • 30
    Great mvc
  • 22
    Powerfull Dependency Injection
  • 18
    Easy to build
  • 13
    Opinionated, batteries-included approach
  • 10
    All in one Framework
  • 7
    Schematics
  • 7
    Solid Standard Setup.
  • 6
    Structured
  • 5
    Performance
  • 3
    Only for single page applications
  • 3
    Complex
  • 1
    Builders
  • 0
    React
CONS OF ANGULAR 2
  • 9
    Overcomplicated
  • 9
    Large overhead in file size and initialization time
  • 2
    Ugly code
  • 2
    Cringe
  • 2
    CLI not open to other test and linting tools

related Angular 2 posts

When Redash was created 5 years ago we chose AngularJS as our frontend framework, but as AngularJS was replaced by Angular 2 we had to make a new choice. We decided that we won't migrate to Angular, but to either React or Vue.js. Eventually we decided to migrate to React for the following reasons:

  1. Many in our community are already using React internally and will be able to contribute.
  2. Using react2angular we can do the migration gradually over time instead of having to invest in a big rewrite while halting feature development.

So far the gradual strategy pays off and in the last 3 major releases we already shipped React code in the Angular.js application.

See more
Max Musing
Founder & CEO at BaseDash | 10 upvotes 路 189.6K views

From my experience of the early startup world, a majority of companies these days use Node.js. Python and Go are the next biggest languages, but significantly smaller than Node.

However, if you're having trouble with the front end aspect of Django, using Node probably won't make that easier for you. You'll have a lot more options between front end frameworks (React, Vue.js, Angular 2) , but they'll definitely take more time to learn than Django's templating system.

Think about whether you want to focus on front end or back end for now, and make a decision from there.

See more
React logo

React

100K
79K
3.8K
A JavaScript library for building user interfaces
100K
79K
+ 1
3.8K
PROS OF REACT
  • 751
    Components
  • 651
    Virtual dom
  • 558
    Performance
  • 484
    Simplicity
  • 436
    Composable
  • 174
    Data flow
  • 159
    Declarative
  • 123
    Isn't an mvc framework
  • 113
    Reactive updates
  • 110
    Explicit app state
  • 31
    JSX
  • 23
    Learn once, write everywhere
  • 18
    Uni-directional data flow
  • 16
    Easy to Use
  • 14
    Works great with Flux Architecture
  • 10
    Great perfomance
  • 8
    Built by Facebook
  • 6
    Javascript
  • 5
    Speed
  • 5
    TypeScript support
  • 4
    Feels like the 90s
  • 4
    Awesome
  • 4
    Scalable
  • 4
    Easy to start
  • 3
    Fancy third party tools
  • 3
    Hooks
  • 3
    Server side views
  • 3
    Functional
  • 2
    Simple
  • 2
    Great migration pathway for older systems
  • 2
    Server Side Rendering
  • 2
    Cross-platform
  • 2
    SSR
  • 2
    Fast evolving
  • 2
    Simple, easy to reason about and makes you productive
  • 2
    Rich ecosystem
  • 2
    Has functional components
  • 2
    Has arrow functions
  • 2
    Strong Community
  • 2
    Closer to standard JavaScript and HTML than others
  • 2
    Very gentle learning curve
  • 2
    Excellent Documentation
  • 2
    Super easy
  • 2
    Props
  • 2
    Scales super well
  • 2
    Just the View of MVC
  • 1
    Www
  • 1
    Start simple
  • 1
    Sdfsdfsdf
  • 1
    Allows creating single page applications
  • 1
    Fragments
  • 1
    Split your UI into components with one true state
  • 1
    Sharable
  • 1
    Every decision architecture wise makes sense
  • 1
    Permissively-licensed
  • 1
    Beautiful and Neat Component Management
  • 1
    Obama
CONS OF REACT
  • 33
    Requires discipline to keep architecture organized
  • 21
    No predefined way to structure your app
  • 20
    Need to be familiar with lots of third party packages
  • 6
    JSX
  • 6
    Not enterprise friendly
  • 1
    One-way binding only
  • 1
    State consistency with backend neglected

related React posts

Vaibhav Taunk
Team Lead at Technovert | 31 upvotes 路 1.5M views

I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

See more
Johnny Bell
Software Engineer at Weedmaps | 26 upvotes 路 412.5K views
Shared insights
on
Vue.js
React

I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.

It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.

See more
Node.js logo

Node.js

110.7K
90.3K
8.3K
A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
110.7K
90.3K
+ 1
8.3K
PROS OF NODE.JS
  • 1.4K
    Npm
  • 1.3K
    Javascript
  • 1.1K
    Great libraries
  • 1K
    High-performance
  • 792
    Open source
  • 481
    Great for apis
  • 472
    Asynchronous
  • 418
    Great community
  • 388
    Great for realtime apps
  • 293
    Great for command line utilities
  • 79
    Node Modules
  • 77
    Websockets
  • 66
    Uber Simple
  • 54
    Great modularity
  • 54
    Allows us to reuse code in the frontend
  • 39
    Easy to start
  • 34
    Great for Data Streaming
  • 30
    Realtime
  • 25
    Awesome
  • 23
    Non blocking IO
  • 17
    Can be used as a proxy
  • 15
    High performance, open source, scalable
  • 14
    Non-blocking and modular
  • 13
    Easy and Fun
  • 12
    Same lang as AngularJS
  • 11
    Easy and powerful
  • 10
    Future of BackEnd
  • 9
    Fast
  • 8
    Cross platform
  • 8
    Fullstack
  • 8
    Scalability
  • 7
    Mean Stack
  • 7
    Simple
  • 5
    React
  • 5
    Great for webapps
  • 5
    Easy concurrency
  • 4
    Friendly
  • 4
    Easy to use and fast and goes well with JSONdb's
  • 4
    Typescript
  • 4
    Fast, simple code and async
  • 3
    Isomorphic coolness
  • 3
    Fast development
  • 3
    Control everything
  • 3
    Its amazingly fast and scalable
  • 3
    Scalable
  • 3
    Great speed
  • 2
    It's fast
  • 2
    Blazing fast
  • 2
    Scales, fast, simple, great community, npm, express
  • 2
    Not Python
  • 2
    TypeScript Support
  • 2
    Easy to learn
  • 2
    Easy to use
  • 2
    Less boilerplate code
  • 2
    Sooper easy for the Backend connectivity
  • 2
    Great community
  • 2
    One language, end-to-end
  • 2
    Javascript2
  • 2
    Performant and fast prototyping
  • 1
    Lovely
  • 1
    Easy
  • 0
    Event Driven
CONS OF NODE.JS
  • 46
    Bound to a single CPU
  • 40
    New framework every day
  • 34
    Lots of terrible examples on the internet
  • 28
    Asynchronous programming is the worst
  • 22
    Callback
  • 16
    Javascript
  • 11
    Dependency based on GitHub
  • 10
    Dependency hell
  • 10
    Low computational power
  • 7
    Can block whole server easily
  • 6
    Very very Slow
  • 6
    Callback functions may not fire on expected sequence
  • 3
    Unneeded over complication
  • 3
    Unstable
  • 3
    Breaking updates
  • 1
    No standard approach

related Node.js posts

Nick Rockwell
SVP, Engineering at Fastly | 42 upvotes 路 1.6M 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
Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber | 38 upvotes 路 3.8M 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
jQuery logo

jQuery

162.6K
45.1K
6.5K
The Write Less, Do More, JavaScript Library.
162.6K
45.1K
+ 1
6.5K
PROS OF JQUERY
  • 1.3K
    Cross-browser
  • 957
    Dom manipulation
  • 805
    Power
  • 660
    Open source
  • 610
    Plugins
  • 457
    Easy
  • 395
    Popular
  • 350
    Feature-rich
  • 281
    Html5
  • 227
    Light weight
  • 91
    Simple
  • 84
    Great community
  • 79
    CSS3 Compliant
  • 69
    Mobile friendly
  • 67
    Fast
  • 43
    Intuitive
  • 42
    Swiss Army knife for webdev
  • 35
    Huge Community
  • 10
    Easy to learn
  • 3
    Clean code
  • 2
    Just awesome
  • 2
    Powerful
  • 2
    Nice
  • 2
    Because of Ajax request :)
  • 1
    Easy Setup
  • 1
    Open Source, Simple, Easy Setup
  • 1
    It Just Works
  • 1
    Improves productivity
  • 1
    Industry acceptance
  • 1
    Allows great manipulation of HTML and CSS
  • 1
    Used everywhere
  • 1
    Widely Used
  • 0
    Javascript
CONS OF JQUERY
  • 5
    Large size
  • 5
    Encourages DOM as primary data source
  • 4
    Sometimes inconsistent API
  • 2
    Live events is overly complex feature

related jQuery posts

Kir Shatrov
Engineering Lead at Shopify | 20 upvotes 路 493.4K views

The client-side stack of Shopify Admin has been a long journey. It started with HTML templates, jQuery and Prototype. We moved to Batman.js, our in-house Single-Page-Application framework (SPA), in 2013. Then, we re-evaluated our approach and moved back to statically rendered HTML and vanilla JavaScript. As the front-end ecosystem matured, we felt that it was time to rethink our approach again. Last year, we started working on moving Shopify Admin to React and TypeScript.

Many things have changed since the days of jQuery and Batman. JavaScript execution is much faster. We can easily render our apps on the server to do less work on the client, and the resources and tooling for developers are substantially better with React than we ever had with Batman.

#FrameworksFullStack #Languages

See more
Ganesa Vijayakumar
Full Stack Coder | Module Lead | 18 upvotes 路 2.3M views

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
PHP logo

PHP

105.6K
50.3K
4.5K
A popular general-purpose scripting language that is especially suited to web development
105.6K
50.3K
+ 1
4.5K
PROS OF PHP
  • 941
    Large community
  • 805
    Open source
  • 757
    Easy deployment
  • 481
    Great frameworks
  • 384
    The best glue on the web
  • 233
    Continual improvements
  • 181
    Good old web
  • 141
    Web foundation
  • 132
    Community packages
  • 123
    Tool support
  • 33
    Used by wordpress
  • 31
    Excellent documentation
  • 26
    Used by Facebook
  • 23
    Because of Symfony
  • 19
    Dynamic Language
  • 14
    Awesome Language and easy to implement
  • 14
    Cheap hosting
  • 14
    Very powerful web language
  • 13
    Fast development
  • 10
    Flexibility, syntax, extensibility
  • 10
    Because of Laravel
  • 10
    Easy to learn
  • 10
    Composer
  • 8
    Easiest deployment
  • 7
    Fastestest Time to Version 1.0 Deployments
  • 7
    Readable Code
  • 7
    Short development lead times
  • 7
    Worst popularity quality ratio
  • 6
    Fast
  • 6
    Most of the web uses it
  • 6
    Faster then ever
  • 5
    Open source and large community
  • 5
    Simple, flexible yet Scalable
  • 4
    Cheap to own
  • 4
    Is like one zip of air
  • 4
    Easy to learn, a big community, lot of frameworks
  • 4
    I have no choice :(
  • 4
    Has the best ecommerce(Magento,Prestashop,Opencart,etc)
  • 4
    Easy to use and learn
  • 4
    Large community, easy setup, easy deployment, framework
  • 4
    Open source and great framework
  • 3
    Great developer experience
  • 2
    Used by STOMT
  • 2
    Fault tolerance
  • 2
    Great flexibility. From fast prototyping to large apps
  • 2
    Interpreted at the run time
  • 2
    FFI
  • 2
    Walk away
  • 2
    Hard not to use
  • 2
    Safe the planet
CONS OF PHP
  • 19
    So easy to learn, good practices are hard to find
  • 16
    Inconsistent API
  • 8
    Fragmented community
  • 5
    Not secure
  • 2
    No routing system
  • 1
    Hard to debug
  • 1
    Old

related PHP posts

Nick Rockwell
SVP, Engineering at Fastly | 42 upvotes 路 1.6M 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
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH | 24 upvotes 路 1.8M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API鈥檚 resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more
Angular CLI logo

Angular CLI

744
589
0
A command line interface for Angular
744
589
+ 1
0
PROS OF ANGULAR CLI
    Be the first to leave a pro
    CONS OF ANGULAR CLI
      Be the first to leave a con

      related Angular CLI posts

      Vaibhav Taunk
      Team Lead at Technovert | 31 upvotes 路 1.5M views

      I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

      See more

      Picked Angular 2 as framework since Angular CLI made it easy to get started on a self-contained frontend web project with TypeScript for easier development -- thanks to intellisense extensions for Visual Studio Code, hassle-free browser compatibility with the built-in Babel transpiler and packaging with the built-in Webpack configuration.

      See more
      Vue.js logo

      Vue.js

      34K
      26.5K
      1.3K
      A progressive framework for building user interfaces
      34K
      26.5K
      + 1
      1.3K
      PROS OF VUE.JS
      • 265
        Simple and easy to start with
      • 206
        Good documentation
      • 178
        Components
      • 118
        Simple the best
      • 95
        Simplified AngularJS
      • 75
        Reactive
      • 66
        Intuitive APIs
      • 47
        Javascript
      • 41
        Changed my front end coding life
      • 37
        Configuration is smooth
      • 26
        Easy to learn
      • 21
        So much fun to use
      • 18
        Progressive
      • 16
        Virtual dom
      • 11
        Faster than bulldogs on hot tarmac
      • 8
        Best of Both Worlds
      • 8
        It's magic
      • 7
        Component is template, javascript and style in one
      • 7
        Without misleading licenses
      • 7
        Application structure
      • 7
        Elegant design
      • 7
        Perfomance
      • 6
        Intuitive and easy to use
      • 5
        Light Weight
      • 4
        Easy to integrate to HTML by inline-templates
      • 4
        Good command line interface
      • 3
        Like Angular only quicker to get started with
      • 3
        Customer Render ending eg to HTML
      • 3
        Small learning curve
      • 2
        Logicless templates
      • 2
        Supports several template languages
      • 2
        High performance
      • 2
        One-way data flow
      • 2
        Single file components
      • 2
        Intuitive
      • 2
        Lots of documentation
      • 2
        Bridge from Web Development to JS Development
      • 2
        Component based
      • 2
        Concise error messages
      • 1
        GUI
      CONS OF VUE.JS
      • 6
        Less Common Place
      • 3
        YXMLvsHTML Markup
      • 1
        Don't support fragments
      • 1
        Only support programatically multiple root nodes

      related Vue.js posts

      Johnny Bell
      Software Engineer at Weedmaps | 26 upvotes 路 412.5K views
      Shared insights
      on
      Vue.js
      React

      I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.

      It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.

      See more
      Shared insights
      on
      Vue.js
      React

      I find using Vue.js to be easier (more concise / less boilerplate) and more intuitive than writing React. However, there are a lot more readily available React components that I can just plug into my projects. I'm debating whether to use Vue.js or React for an upcoming project that I'm going to use to help teach a friend how to build an interactive frontend. Which would you recommend I use?

      See more