Alternatives to redux-saga logo

Alternatives to redux-saga

redux-thunk, redux-saga, MobX, GraphQL, and Redux are the most popular alternatives and competitors to redux-saga.
258
181
+ 1
4

What is redux-saga and what are its top alternatives?

An alternative side effect model for Redux apps
redux-saga is a tool in the State Management Library category of a tech stack.
redux-saga is an open source tool with 20.1K GitHub stars and 1.8K GitHub forks. Here鈥檚 a link to redux-saga's open source repository on GitHub

Top Alternatives of redux-saga

redux-saga alternatives & related posts

redux-thunk logo

redux-thunk

120
78
0
120
78
+ 1
0
Thunk middleware for Redux
    Be the first to leave a pro
    redux-thunk logo
    redux-thunk
    VS
    redux-saga logo
    redux-saga

    related redux-thunk posts

    redux-saga
    redux-saga
    Redux
    Redux
    React
    React
    redux-thunk
    redux-thunk
    Jest
    Jest

    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
    React
    React
    redux-saga
    redux-saga
    redux-thunk
    redux-thunk
    Redux
    Redux
    #Redux-saga

    For async requests in React I use redux-saga , to my opinion it is the most organized framework for async requests, it is clearer then redux-thunk and conforms to the style of Redux.js which results in a more structured project, especially in large web applications. #redux-saga

    See more
    redux-saga logo

    redux-saga

    258
    181
    4
    258
    181
    + 1
    4
    An alternative side effect model for Redux apps
    redux-saga logo
    redux-saga
    VS
    redux-saga logo
    redux-saga

    related redux-saga posts

    React
    React
    Redux
    Redux
    AngularJS
    AngularJS
    React Native
    React Native
    redux-saga
    redux-saga
    Apache Cordova
    Apache Cordova
    #JavascriptMvcFrameworks

    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
    redux-saga
    redux-saga
    Redux
    Redux
    React
    React
    redux-thunk
    redux-thunk
    Jest
    Jest

    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

    related MobX posts

    Gianluca Bargelli
    Gianluca Bargelli
    React
    React
    AngularJS
    AngularJS
    Redux
    Redux
    MobX
    MobX

    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
    Johnny Bell
    Johnny Bell
    Senior Software Engineer at StackShare | 9 upvotes 149.9K views
    atStackShareStackShare
    jQuery
    jQuery
    React
    React
    ES6
    ES6
    JavaScript
    JavaScript
    MobX
    MobX
    GraphQL
    GraphQL
    Apollo
    Apollo
    #Hooks馃帲
    #Context

    We are always building new features and replacing old code at StackShare. Lately we have been building out new features for the frontend, and removing a lot of old jQuery code (sorry jQuery but it's time to go).

    We've mainly been using React, ES6 and JavaScript on the frontend to build out the components, and we've been slowly removing some legacy MobX and using GraphQL and Apollo for our state management, if we need to control state further than GraphQL and Apollo allows us to we use just plain React with #context , or the new fancy React #hooks馃帲 .

    As we've moved towards the above tech, its really made smashing out new features and updating legacy code super fast, and really fun!

    See more

    related GraphQL posts

    Node.js
    Node.js
    GraphQL
    GraphQL
    MongoDB
    MongoDB

    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
    Nick Rockwell
    CTO at NY Times | 30 upvotes 886.9K views
    atThe New York TimesThe New York Times
    MySQL
    MySQL
    PHP
    PHP
    React
    React
    Apollo
    Apollo
    GraphQL
    GraphQL
    Node.js
    Node.js
    Kafka
    Kafka
    Apache HTTP Server
    Apache HTTP Server

    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

    related Redux posts

    Johnny Bell
    Johnny Bell
    Senior Software Engineer at StackShare | 58 upvotes 564.9K views
    Firebase
    Firebase
    React
    React
    Redux
    Redux
    styled-components
    styled-components
    Netlify
    Netlify
    Gatsby
    Gatsby
    GitHub
    GitHub
    #ReactRally
    #Frontend
    #Google

    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
    Ruby
    Ruby
    Rails
    Rails
    React
    React
    Redux
    Redux
    Create React App
    Create React App
    Jest
    Jest
    react-testing-library
    react-testing-library
    RSpec
    RSpec
    PostgreSQL
    PostgreSQL
    MongoDB
    MongoDB
    Redis
    Redis
    React Native
    React Native
    Next.js
    Next.js
    Python
    Python
    Bit
    Bit
    JavaScript
    JavaScript

    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
    vuex logo

    vuex

    635
    497
    3
    635
    497
    + 1
    3
    Centralized State Management for Vue.js.
    vuex logo
    vuex
    VS
    redux-saga logo
    redux-saga

    related vuex posts

    Rails
    Rails
    Sidekiq
    Sidekiq
    PostgreSQL
    PostgreSQL
    Redis
    Redis
    MongoDB
    MongoDB
    Vue.js
    Vue.js
    vuex
    vuex
    jQuery
    jQuery
    React
    React
    Redux
    Redux
    Yarn
    Yarn
    #Bulma.io
    #Font-awesome

    I'm building a new process management tool. I decided to build with Rails as my backend, using Sidekiq for background jobs. I chose to work with these tools because I've worked with them before and know that they're able to get the job done. They may not be the sexiest tools, but they work and are reliable, which is what I was optimizing for. For data stores, I opted for PostgreSQL and Redis. Because I'm planning on offering dashboards, I wanted a SQL database instead of something like MongoDB that might work early on, but be difficult to use as soon as I want to facilitate aggregate queries.

    On the front-end I'm using Vue.js and vuex in combination with #Turbolinks. In effect, I want to render most pages on the server side without key interactions being managed by Vue.js . This is the first project I'm working on where I've explicitly decided not to include jQuery . I have found React and Redux.js more confusing to setup. I appreciate the opinionated approach from the Vue.js community and that things just work together the way that I'd expect. To manage my javascript dependencies, I'm using Yarn .

    For CSS frameworks, I'm using #Bulma.io. I really appreciate it's minimal nature and that there are no hard javascript dependencies. And to add a little spice, I'm using #font-awesome.

    See more
    reselect logo

    reselect

    37
    15
    0
    37
    15
    + 1
    0
    Selector library for Redux
      Be the first to leave a pro
      reselect logo
      reselect
      VS
      redux-saga logo
      redux-saga
      Redux Observable logo

      Redux Observable

      28
      13
      0
      28
      13
      + 1
      0
      A powerful middleware for Redux using RxJS
        Be the first to leave a pro
        Redux Observable logo
        Redux Observable
        VS
        redux-saga logo
        redux-saga