Alternatives to React Redux logo

Alternatives to React Redux

React, React Native, Angular 2, Flux, and MobX are the most popular alternatives and competitors to React Redux.
867
761
+ 1
0

What is React Redux and what are its top alternatives?

It is the official React binding for Redux. It lets your React components read data from a Redux store, and dispatch actions to the store to update data. It is designed to work with React's component model. You define how to extract the values your component needs from Redux, and your component receives them as props.
React Redux is a tool in the Javascript Utilities & Libraries category of a tech stack.
React Redux is an open source tool with GitHub stars and GitHub forks. Here’s a link to React Redux's open source repository on GitHub

Top Alternatives to React Redux

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

  • React Native
    React Native

    React Native enables you to build world-class application experiences on native platforms using a consistent developer experience based on JavaScript and React. The focus of React Native is on developer efficiency across all the platforms you care about - learn once, write anywhere. Facebook uses React Native in multiple production apps and will continue investing in React Native. ...

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

  • Flux
    Flux

    Flux is the application architecture that Facebook uses for building client-side web applications. It complements React's composable view components by utilizing a unidirectional data flow. It's more of a pattern rather than a formal framework, and you can start using Flux immediately without a lot of new 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. ...

  • Apollo
    Apollo

    Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes. ...

  • RxJS
    RxJS

    RxJS is a library for reactive programming using Observables, to make it easier to compose asynchronous or callback-based code. This project is a rewrite of Reactive-Extensions/RxJS with better performance, better modularity, better debuggable call stacks, while staying mostly backwards compatible, with some breaking changes that reduce the API surface. ...

  • Modernizr
    Modernizr

    It’s a collection of superfast tests or detects as we like to call them which run as your web page loads, then you can use the results to tailor the experience to the user. It tells you what HTML, CSS and JavaScript features the user’s browser has to offer. ...

React Redux alternatives & related posts

React logo

React

128.9K
105.1K
3.9K
A JavaScript library for building user interfaces
128.9K
105.1K
+ 1
3.9K
PROS OF REACT
  • 775
    Components
  • 658
    Virtual dom
  • 567
    Performance
  • 492
    Simplicity
  • 438
    Composable
  • 176
    Data flow
  • 162
    Declarative
  • 124
    Isn't an mvc framework
  • 114
    Reactive updates
  • 111
    Explicit app state
  • 40
    JSX
  • 24
    Learn once, write everywhere
  • 19
    Uni-directional data flow
  • 17
    Easy to Use
  • 14
    Works great with Flux Architecture
  • 10
    Great perfomance
  • 8
    Built by Facebook
  • 7
    Javascript
  • 5
    Speed
  • 5
    TypeScript support
  • 4
    Easy to start
  • 4
    Scalable
  • 4
    Awesome
  • 4
    Feels like the 90s
  • 4
    Hooks
  • 3
    Excellent Documentation
  • 3
    Scales super well
  • 3
    Functional
  • 3
    Obama
  • 3
    Fancy third party tools
  • 3
    Server side views
  • 3
    Props
  • 3
    Server Side Rendering
  • 3
    Cross-platform
  • 2
    Rich ecosystem
  • 2
    Start simple
  • 2
    Allows creating single page applications
  • 2
    Sdfsdfsdf
  • 2
    Beautiful and Neat Component Management
  • 2
    Very gentle learning curve
  • 2
    Has functional components
  • 2
    Simple
  • 2
    Closer to standard JavaScript and HTML than others
  • 2
    Super easy
  • 2
    Has arrow functions
  • 2
    Strong Community
  • 2
    Great migration pathway for older systems
  • 2
    SSR
  • 2
    Fast evolving
  • 2
    Simple, easy to reason about and makes you productive
  • 2
    Just the View of MVC
  • 1
    Sharable
  • 1
    Every decision architecture wise makes sense
  • 1
    Permissively-licensed
  • 1
    Split your UI into components with one true state
  • 1
    Fragments
  • 0
    Recharts
CONS OF REACT
  • 36
    Requires discipline to keep architecture organized
  • 23
    No predefined way to structure your app
  • 22
    Need to be familiar with lots of third party packages
  • 9
    JSX
  • 7
    Not enterprise friendly
  • 5
    One-way binding only
  • 2
    State consistency with backend neglected
  • 2
    Bad Documentation
  • 1
    Paradigms change too fast

related React posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.9M 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
Adebayo Akinlaja
Engineering Manager at Andela · | 27 upvotes · 1.1M views

I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

See more
React Native logo

React Native

25.9K
22.5K
1.1K
A framework for building native apps with React
25.9K
22.5K
+ 1
1.1K
PROS OF REACT NATIVE
  • 204
    Learn once write everywhere
  • 166
    Cross platform
  • 162
    Javascript
  • 118
    Native ios components
  • 67
    Built by facebook
  • 62
    Easy to learn
  • 43
    Bridges me into ios development
  • 40
    It's just react
  • 39
    No compile
  • 36
    Declarative
  • 21
    Fast
  • 12
    Virtual Dom
  • 12
    Livereload
  • 11
    Insanely fast develop / test cycle
  • 10
    Great community
  • 9
    Easy setup
  • 9
    Backed by Facebook
  • 9
    It is free and open source
  • 8
    Native android components
  • 7
    Highly customizable
  • 6
    Scalable
  • 6
    Everything component
  • 6
    Awesome
  • 6
    Win win solution of hybrid app
  • 6
    Great errors
  • 5
    Not dependent on anything such as Angular
  • 5
    Simple
  • 4
    OTA update
  • 4
    Awesome, easy starting from scratch
  • 3
    Easy to use
  • 3
    As good as Native without any performance concerns
  • 2
    Web development meets Mobile development
  • 2
    Hot reload
  • 2
    Over the air update (Flutter lacks)
  • 2
    'It's just react'
  • 2
    Many salary
  • 2
    Can be incrementally added to existing native apps
  • 1
    Nigger
  • 1
    Cons
  • 1
    Ngon
  • 0
    Ful
CONS OF REACT NATIVE
  • 23
    Javascript
  • 18
    Built by facebook
  • 12
    Cant use CSS
  • 4
    30 FPS Limit
  • 2
    Slow
  • 2
    Some compenents not truly native
  • 2
    Generate large apk even for a simple app

related React Native posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.9M 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

I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis  for cache and other time sensitive operations.

We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.

See more
Angular 2 logo

Angular 2

4.9K
3.9K
453
A platform for building mobile and desktop web applications
4.9K
3.9K
+ 1
453
PROS OF ANGULAR 2
  • 100
    It's a powerful framework
  • 49
    Straight-forward architecture
  • 42
    TypeScript
  • 41
    Great UI and Business Logic separation
  • 39
    Powerful, maintainable, fast
  • 37
    Amazing CLI
  • 31
    Great mvc
  • 24
    Powerfull Dependency Injection
  • 18
    Easy to build
  • 14
    Opinionated, batteries-included approach
  • 12
    All in one Framework
  • 9
    Schematics
  • 8
    Solid Standard Setup.
  • 7
    Performance
  • 7
    Structured
  • 4
    Complex
  • 4
    Only for single page applications
  • 3
    Builders
  • 2
    Ng upgrade
  • 2
    RxJS
  • 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 · 375.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
Flux logo

Flux

479
484
130
Application Architecture for Building User Interfaces
479
484
+ 1
130
PROS OF FLUX
  • 44
    Unidirectional data flow
  • 32
    Architecture
  • 19
    Structure and Data Flow
  • 14
    Not MVC
  • 12
    Open source
  • 6
    Created by facebook
  • 3
    A gestalt shift
CONS OF FLUX
    Be the first to leave a con

    related Flux posts

    Marcos Iglesias
    Sr. Software Engineer at Eventbrite · | 13 upvotes · 172.6K views

    We are in the middle of a change of the stack on the front end. So we used Backbone.js with Marionette. Then we also created our own implementation of a Flux kind of flow. We call it eb-flux. We have worked with Marionette for a long time. Then at some point we start evolving and end up having a kind of Redux.js-style architecture, but with Marionette.

    But then maybe one and a half years ago, we started moving into React and that's why we created the Eventbrite design system. It's a really nice project that probably could be open sourced. It's a library of components for our React components.

    With the help of that library, we are building our new stack with React and sometimes Redux when it's necessary.

    See more
    MobX logo

    MobX

    629
    471
    114
    Simple, scalable state management
    629
    471
    + 1
    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
    Apollo logo

    Apollo

    2.1K
    1.6K
    19
    GraphQL server for Express, Connect, Hapi, Koa and more
    2.1K
    1.6K
    + 1
    19
    PROS OF APOLLO
    • 12
      From the creators of Meteor
    • 3
      Great documentation
    • 2
      Open source
    • 2
      Real time if use subscription
    CONS OF APOLLO
      Be the first to leave a con

      related Apollo posts

      Nick Rockwell
      SVP, Engineering at Fastly · | 44 upvotes · 1.9M 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
      Adam Neary

      At Airbnb we use GraphQL Unions for a "Backend-Driven UI." We have built a system where a very dynamic page is constructed based on a query that will return an array of some set of possible “sections.” These sections are responsive and define the UI completely.

      The central file that manages this would be a generated file. Since the list of possible sections is quite large (~50 sections today for Search), it also presumes we have a sane mechanism for lazy-loading components with server rendering, which is a topic for another post. Suffice it to say, we do not need to package all possible sections in a massive bundle to account for everything up front.

      Each section component defines its own query fragment, colocated with the section’s component code. This is the general idea of Backend-Driven UI at Airbnb. It’s used in a number of places, including Search, Trip Planner, Host tools, and various landing pages. We use this as our starting point, and then in the demo show how to (1) make and update to an existing section, and (2) add a new section.

      While building your product, you want to be able to explore your schema, discovering field names and testing out potential queries on live development data. We achieve that today with GraphQL Playground, the work of our friends at #Prisma. The tools come standard with Apollo Server.

      #BackendDrivenUI

      See more
      RxJS logo

      RxJS

      2K
      562
      18
      The Reactive Extensions for JavaScript
      2K
      562
      + 1
      18
      PROS OF RXJS
      • 4
        Easier async data chaining and combining
      • 3
        Steep learning curve, but offers predictable operations
      • 2
        Easier testing
      • 2
        Ability to build your own stream
      • 2
        Works great with any state management implementation
      • 1
        Simplifies state management
      • 1
        Great for push based architecture
      • 1
        Observable subjects
      • 1
        Documentation
      • 1
        Lot of build-in operators
      CONS OF RXJS
      • 3
        Steep learning curve

      related RxJS posts

      Modernizr logo

      Modernizr

      26.7K
      1.6K
      0
      Respond to your user’s browser features
      26.7K
      1.6K
      + 1
      0
      PROS OF MODERNIZR
        Be the first to leave a pro
        CONS OF MODERNIZR
          Be the first to leave a con

          related Modernizr posts