Alternatives to RxJS logo

Alternatives to RxJS

React, Ramda, MobX, redux-saga, and axios are the most popular alternatives and competitors to RxJS.
2.1K
631
+ 1
21

What is RxJS and what are its top alternatives?

RxJS is a popular library for reactive programming in JavaScript, providing developers with powerful tools for manipulating asynchronous data streams. Its key features include observables, operators for transforming, combining, and filtering data, and seamless integration with various frameworks like Angular. However, its learning curve can be steep for beginners, and complex applications may require advanced knowledge to manage data flows efficiently.

  1. Most.js: Most.js is a super-powered stream library with a strong focus on performance and minimal bundle size. It offers similar functionalities to RxJS, but with a simpler API and better performance. Pros: Leaner library, better performance. Cons: Smaller community than RxJS.
  2. Kefir.js: Kefir.js is a functional reactive library with a simple and intuitive API. It provides tools for working with continuous streams of data and handling complex event flows. Pros: Easy to learn, intuitive API. Cons: Not as feature-rich as RxJS.
  3. Bacon.js: Bacon.js is another functional reactive library that emphasizes event stream composition and transformation. It offers a straightforward API for working with reactive streams and handling asynchronous events. Pros: Easy to use, good documentation. Cons: Lacks some advanced features compared to RxJS.
  4. Xstream: Xstream is a fast and flexible library for reactive programming, focusing on high performance and scalability. It provides a simple API for creating and managing streams of data in JavaScript applications. Pros: High performance, simple API. Cons: Limited ecosystem compared to RxJS.
  5. ReactiveX/RxJS: This is the official RxJS Github repository.

Top Alternatives to RxJS

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

  • Ramda
    Ramda

    It emphasizes a purer functional style. Immutability and side-effect free functions are at the heart of its design philosophy. This can help you get the job done with simple, elegant code. ...

  • MobX
    MobX

    MobX is a battle tested library that makes state management simple and scalable by transparently applying functional reactive programming (TFRP). React and MobX together are a powerful combination. React renders the application state by providing mechanisms to translate it into a tree of renderable components. MobX provides the mechanism to store and update the application state that React then uses. ...

  • redux-saga
    redux-saga

    An alternative side effect model for Redux apps

  • axios
    axios

    It is a Javascript library used to make http requests from node.js or XMLHttpRequests from the browser and it supports the Promise API that is native to JS ES6. ...

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

RxJS alternatives & related posts

React logo

React

173.3K
4.1K
A JavaScript library for building user interfaces
173.3K
4.1K
PROS OF REACT
  • 832
    Components
  • 673
    Virtual dom
  • 578
    Performance
  • 508
    Simplicity
  • 442
    Composable
  • 186
    Data flow
  • 166
    Declarative
  • 128
    Isn't an mvc framework
  • 120
    Reactive updates
  • 115
    Explicit app state
  • 50
    JSX
  • 29
    Learn once, write everywhere
  • 22
    Easy to Use
  • 21
    Uni-directional data flow
  • 17
    Works great with Flux Architecture
  • 11
    Great perfomance
  • 10
    Javascript
  • 9
    Built by Facebook
  • 8
    TypeScript support
  • 6
    Server Side Rendering
  • 6
    Speed
  • 5
    Feels like the 90s
  • 5
    Excellent Documentation
  • 5
    Props
  • 5
    Functional
  • 5
    Easy as Lego
  • 5
    Closer to standard JavaScript and HTML than others
  • 5
    Cross-platform
  • 5
    Easy to start
  • 5
    Hooks
  • 5
    Awesome
  • 5
    Scalable
  • 4
    Super easy
  • 4
    Allows creating single page applications
  • 4
    Server side views
  • 4
    Sdfsdfsdf
  • 4
    Start simple
  • 4
    Strong Community
  • 4
    Fancy third party tools
  • 4
    Scales super well
  • 3
    Has arrow functions
  • 3
    Beautiful and Neat Component Management
  • 3
    Just the View of MVC
  • 3
    Simple, easy to reason about and makes you productive
  • 3
    Fast evolving
  • 3
    SSR
  • 3
    Great migration pathway for older systems
  • 3
    Rich ecosystem
  • 3
    Simple
  • 3
    Has functional components
  • 3
    Every decision architecture wise makes sense
  • 3
    Very gentle learning curve
  • 2
    Split your UI into components with one true state
  • 2
    Image upload
  • 2
    Permissively-licensed
  • 2
    Fragments
  • 2
    Sharable
  • 2
    Recharts
  • 2
    HTML-like
  • 1
    React hooks
  • 1
    Datatables
CONS OF REACT
  • 41
    Requires discipline to keep architecture organized
  • 30
    No predefined way to structure your app
  • 29
    Need to be familiar with lots of third party packages
  • 13
    JSX
  • 10
    Not enterprise friendly
  • 6
    One-way binding only
  • 3
    State consistency with backend neglected
  • 3
    Bad Documentation
  • 2
    Error boundary is needed
  • 2
    Paradigms change too fast

related React posts

Johnny Bell

I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

See more
Collins Ogbuzuru
Front-end dev at Evolve credit · | 38 upvotes · 267.1K views

Your tech stack is solid for building a real-time messaging project.

React and React Native are excellent choices for the frontend, especially if you want to have both web and mobile versions of your application share code.

ExpressJS is an unopinionated framework that affords you the flexibility to use it's features at your term, which is a good start. However, I would recommend you explore Sails.js as well. Sails.js is built on top of Express.js and it provides additional features out of the box, especially the Websocket integration that your project requires.

Don't forget to set up Graphql codegen, this would improve your dev experience (Add Typescript, if you can too).

I don't know much about databases but you might want to consider using NO-SQL. I used Firebase real-time db and aws dynamo db on a few of my personal projects and I love they're easy to work with and offer more flexibility for a chat application.

See more
Ramda logo

Ramda

290
3
A practical functional library for JavaScript programmers
290
3
PROS OF RAMDA
  • 2
    Automatically curried
  • 1
    Point free programming
CONS OF RAMDA
    Be the first to leave a con

    related Ramda posts

    MobX logo

    MobX

    748
    114
    Simple, scalable state management
    748
    114
    PROS OF MOBX
    • 26
      It's just stupidly simple, yet so magical
    • 18
      Easier and cleaner than Redux
    • 15
      Fast
    • 13
      Automagic updates
    • 13
      React integration
    • 10
      Computed properties
    • 8
      ES6 observers and obversables
    • 7
      Global stores
    • 3
      Flexible architecture the requeriment
    • 1
      Has own router package (mobx-router)
    CONS OF MOBX
    • 1
      Maturity

    related MobX posts

    Dan Robinson

    The front end for Heap begun to grow unwieldy. The original jQuery pieces became difficult to maintain and scale, and a decision was made to introduce Backbone.js, Marionette, and TypeScript. Ultimately this ended up being a “detour” in the search for a scalable and maintainable front-end solution. The system did allow for developers to reuse components efficiently, but adding features was a difficult process, and it eventually became a bottleneck in advancing the product.

    Today, the Heap product consists primarily of a customer-facing dashboard powered by React, MobX, and TypeScript on the front end. We wrote our migration to React and MobX in detail last year here.

    #JavascriptUiLibraries #Libraries #JavascriptMvcFrameworks #TemplatingLanguagesExtensions

    See more

    We started rebuilding our dashboard components using React from AngularJS over 3 years ago and, in order to have predictable client-side state management we introduced Redux.js inside our stack because of the popularity it gained inside the JavaScript community; that said, the number of lines of codes needed to implement even the simplest form was unnecessarily high, from a simple form to a more complex component like our team management page.

    By switching our state management to MobX we removed approximately 40% of our boilerplate code and simplified our front-end development flow, which in the ends allowed us to focus more into product features rather than architectural choices.

    See more
    redux-saga logo

    redux-saga

    425
    8
    An alternative side effect model for Redux apps
    425
    8
    PROS OF REDUX-SAGA
    • 7
      Easy to test
    • 1
      Easy to learn
    CONS OF REDUX-SAGA
      Be the first to leave a con

      related redux-saga posts

      We had contemplated a long time which #JavascriptMvcFrameworks to use, React and React Native vs AngularJS and Apache Cordova in both web and mobile. Eventually we chose react over angular since it was quicker to learn, less code for simple apps and quicker integration of third party javascript modules. for the full MVC we added Redux.js for state management and redux-saga for async calls and logic. since we also have mobile app along with the web, we can shere logic and model between web and mobile.

      See more

      Choosing redux-saga for my async Redux.js middleware, for a React application, instead of the typical redux-thunk .

      Redux-saga is much easier to test than Redux-thunk - it requires no module mocking at all. Converting from redux-thunk to redux-saga is easy enough, as you are only refactoring the action creators - not your redux store or your react components. I've linked a github repo that shows the same solution with both, including Jest tests.

      See more
      axios logo

      axios

      3.4K
      0
      Promise based HTTP client for the browser and node.js
      3.4K
      0
      PROS OF AXIOS
        Be the first to leave a pro
        CONS OF AXIOS
          Be the first to leave a con

          related axios posts

          I built a project using Quasar Framework with Vue.js, vuex and axios on the frontend and Go, Gin Gonic and PostgreSQL on the backend. Deployment was realized using Docker and Docker Compose. Now I can build the desktop and the mobile app using a single code base on the frontend. UI responsiveness and performance of this stack is amazing.

          See more
          Shared insights
          on
          Vue RouterVue Routeraxiosaxios

          hello, I'm a newbie. is axios the same as Vue Router? Or can /should use both? thanks

          See more
          JavaScript logo

          JavaScript

          361.2K
          8.1K
          Lightweight, interpreted, object-oriented language with first-class functions
          361.2K
          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
          • 746
            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
            Future Language of The Web
          • 12
            Setup is easy
          • 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
            Easy
          • 9
            Can be used in backend, frontend and DB
          • 9
            Expansive community
          • 9
            Everyone use it
          • 8
            Easy to hire developers
          • 8
            Most Popular Language in the World
          • 8
            For the good parts
          • 8
            Can be used both as frontend and backend as well
          • 8
            No need to use PHP
          • 8
            Powerful
          • 7
            Evolution of C
          • 7
            Its fun and fast
          • 7
            It's fun
          • 7
            Nice
          • 7
            Versitile
          • 7
            Hard not to use
          • 7
            Popularized Class-Less Architecture & Lambdas
          • 7
            Agile, packages simple to use
          • 7
            Supports lambdas and closures
          • 7
            Love-hate relationship
          • 7
            Photoshop has 3 JS runtimes built in
          • 6
            1.6K Can be used on frontend/backend
          • 6
            Client side JS uses the visitors CPU to save Server Res
          • 6
            It let's me use Babel & Typescript
          • 6
            Easy to make something
          • 6
            Can be used on frontend/backend/Mobile/create PRO Ui
          • 5
            Client processing
          • 5
            What to add
          • 5
            Everywhere
          • 5
            Scope manipulation
          • 5
            Function expressions are useful for callbacks
          • 5
            Stockholm Syndrome
          • 5
            Promise relationship
          • 5
            Clojurescript
          • 4
            Only Programming language on browser
          • 4
            Because it is so simple and lightweight
          • 1
            Easy to learn and test
          • 1
            Easy to understand
          • 1
            Not the best
          • 1
            Subskill #4
          • 1
            Hard to learn
          • 1
            Test2
          • 1
            Test
          • 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.7M 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

          245K
          6.9K
          A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
          245K
          6.9K
          PROS OF PYTHON
          • 1.2K
            Great libraries
          • 963
            Readable code
          • 847
            Beautiful code
          • 788
            Rapid development
          • 691
            Large community
          • 438
            Open source
          • 393
            Elegant
          • 282
            Great community
          • 273
            Object oriented
          • 221
            Dynamic typing
          • 77
            Great standard library
          • 60
            Very fast
          • 55
            Functional programming
          • 50
            Easy to learn
          • 46
            Scientific computing
          • 35
            Great documentation
          • 29
            Productivity
          • 28
            Matlab alternative
          • 28
            Easy to read
          • 24
            Simple is better than complex
          • 20
            It's the way I think
          • 19
            Imperative
          • 18
            Very programmer and non-programmer friendly
          • 18
            Free
          • 17
            Machine learning support
          • 17
            Powerfull language
          • 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
            Import antigravity
          • 8
            It's lean and fun to code
          • 7
            Print "life is short, use python"
          • 7
            Python has great libraries for data processing
          • 6
            High Documented language
          • 6
            I love snakes
          • 6
            Readability counts
          • 6
            Rapid Prototyping
          • 6
            Now is better than never
          • 6
            Although practicality beats purity
          • 6
            Flat is better than nested
          • 6
            Great for tooling
          • 6
            There should be one-- and preferably only one --obvious
          • 6
            Fast coding and good for competitions
          • 5
            Web scraping
          • 5
            Lists, tuples, dictionaries
          • 5
            Great for analytics
          • 4
            Beautiful is better than ugly
          • 4
            Easy to learn and use
          • 4
            Easy to setup and run smooth
          • 4
            Multiple Inheritence
          • 4
            CG industry needs
          • 4
            Socially engaged community
          • 4
            Complex is better than complicated
          • 4
            Plotting
          • 4
            Simple and easy to learn
          • 3
            List comprehensions
          • 3
            Powerful language for AI
          • 3
            Flexible and easy
          • 3
            It is Very easy , simple and will you be love programmi
          • 3
            Many types of collections
          • 3
            If the implementation is easy to explain, it may be a g
          • 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
            No cruft
          • 3
            Generators
          • 3
            Import this
          • 2
            Batteries included
          • 2
            Securit
          • 2
            Can understand easily who are new to programming
          • 2
            Should START with this but not STICK with This
          • 2
            A-to-Z
          • 2
            Because of Netflix
          • 2
            Only one way to do it
          • 2
            Better outcome
          • 2
            Good for hacking
          • 1
            Best friend for NLP
          • 1
            Sexy af
          • 1
            Procedural programming
          • 1
            Automation friendly
          • 1
            Slow
          • 0
            Keep it simple
          • 0
            Powerful
          • 0
            Ni
          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.7M 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.8K
          8.5K
          A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
          188.8K
          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
          • 424
            Great community
          • 390
            Great for realtime apps
          • 296
            Great for command line utilities
          • 85
            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
          Anurag Maurya

          Needs advice on code coverage tool in Node.js/ExpressJS with External API Testing Framework

          Hello community,

          I have a web application with the backend developed using Node.js and Express.js. The backend server is in one directory, and I have a separate API testing framework, made using SuperTest, Mocha, and Chai, in another directory. The testing framework pings the API, retrieves responses, and performs validations.

          I'm currently looking for a code coverage tool that can accurately measure the code coverage of my backend code when triggered by the API testing framework. I've tried using Istanbul and NYC with instrumented code, but the results are not as expected.

          Could you please recommend a reliable code coverage tool or suggest an approach to effectively measure the code coverage of my Node.js/Express.js backend code in this setup?

          See more