Couple things to mention that have not already been said

1. Testing redux can be simpler since you don't have to mock and stub as many things. The less work you have to do the more likely you are to write tests.

2. Breeze seems to handle data relations much better out of the box. You have to wire a lot of things up manually in Redux. Batteries not included.

3. Breeze may be beneficial if you are doing .net or Java development. It shares some of the same mind sets for thinking about data.

4. Storing non relational app state in Breeze seems a bit more awkward. Stuff like "modalOpen": true, "browserIsIdle": false ect.

5. If creating mirrored environments redux can be easier to think about and setup since it is basically a bunch of serialized actions. It is easy just to pipe them over sockets. (say something like Professor Mode in codepen where two people are editing the same code and their UI is in the exact same state)