To answer the original question here, while Ember Data and Ember Redux aren’t mutually exclusive (just as using Ember Data and regular Ajax calls for JSON payloads aren’t mutually exclusive), it may get more complicated if you run both in your app.
Ember Redux (from what I’ve seen) gives you quite a bit of control at quite granular levels over how your data updates and when. If you know you need that (or strongly suspect you do), then go ahead and use it. Ember’s designed to allow working with a wide variety of data management systems. But Ember Redux is on the cutting/bleeding edge of Ember’s data handling approach, which means if you don’t know if you need it it may be wiser to stick with the tried and true defaults.
If your main interest in Ember Redux is due to anxiety about not being left behind (or getting out of date), then I would suggest reading https://blog.embermap.com/safety-of-the-herd-8d64f9170299 It’s a clear articulation of the idea that most of the time with Ember, the defaults are “good enough” and are well-maintained while new ideas are considered and incorporated into the Ember defaults.
That doesn’t mean that there aren’t warts and flaws to what exist in Ember (there are!), but that often those issues are better understood within the Ember community than the cutting edge addons. Over time cutting edge ideas get incorporated into the defaults in Ember so that we can all use them.
Put another way: what is your risk tolerance/comfort level with cutting edge? and is that cutting edge stuff needed in the app you are working on? If it is, awesome and go for it. If not, choose boring tech … http://mcfunley.com/choose-boring-technology
Does that help at all?