Recoil VS zedux

Atom-based: splits states into tiny pieces of data called atoms, which can be written to and read from using React hooks. In this group, we have Recoil and Jotai.

recoil -> Designed to solve a specific problem. Not good for all use cases. Understand it first! You can learn more about it here.

Recoil Official Website

Recoil 🌀

Atomic libs include Recoil, Jotai, and the one I maintain: Zedux. Zedux especially was designed to work well with sockets and RxJS observables and has been getting some traction recently, so of course I recommend checking it out. Feel free to hmu with any questions.

However you may find better luck with Recoil which is developed by Meta, and is designed to work with Async data, and is a much simpler project to get started with.

Recoil introduced a new pattern for storing state and propagating updates. This atomic model has proven to scale up better than the singleton model at the cost of some hefty learning curves.

recoil is extremely similar to Riverpod but for React (both are backed by a data flow graph).

Before we proceed you can check the project on github. This implementation is for learning purposes, for production use check Jotai or Recoil.

Atomic libs include Recoil, Jotai, and the one I maintain: Zedux. Zedux especially was designed to work well with sockets and RxJS observables and has been getting some traction recently, so of course I recommend checking it out. Feel free to hmu with any questions.

This new tool started driving our production apps in early 2021 and has been a lifesaver in the extremes of complexity. 2 years later, we have finally open-sourced this tool as "Zedux".

Zedux is a hybrid tool similar to RTK + RTKQ but with first-class DI support.

For atoms, Jotai or Zedux

Zedux is a new up-and-coming hybrid tool similar to RTK + RTK Query but with atoms

Atomic libraries like Recoil, Jotai, and Zedux specialize in expressing these dependencies clearly, giving you insight into your dependency graph and offering tools like evaluation tracing, time travel, and DI overrides to improve testability and discoverability of your code.

I'd recommend a powerful state management library for something like this, especially one that gives you full control over async flow outside React. Here's a codesandbox using Zedux to demonstrate sending 4 buffered requests per minute.

After Zustand, if you need anything more, I'd either go back to Redux or learn Jotai, an atomic library that's a little more powerful than Zustand. Atoms are a little more advanced, so I wouldn't start there. Though (full disclosure) I am the author of another atomic library that is aiming to make atoms simpler to learn and use. Someday we'll get there, but for now I'd say Zustand is the best place to start.

Source: I'm the creator of Zedux, a lib that we just publicly released a few days ago and drives lots of highly-volatile state like this in our apps. If you need a powerful state manager designed to work at scale with fast-moving state streamed over websockets (SSEs work too), it might be worth looking into. Cheers!

GitHub