For me, I tend to put `node-fetch` onto `global.fetch` so that it's generally available like in modern browsers. If you have to support older browsers, could always use `isomorphic-fetch` for shared modules. I prefer to assume it's globally available and write to that.
It's not exactly the same, but close enough that I rarely have issue with client-server modules.
Nice... another heavy hitter using React not mentioned in the article would be Walmart, who has done a lot for optimized server/client and doughnut rendering.
While cool... much like ngrx, this is emphatically no longer redux in my mind, and shouldn't be labelled as such. There are a lot of similar frameworks, and they are cool but I can't help but feel they are trying to piggy back a different pattern off of redux's success.
Updated article link to the github repo, which points to the website. Since the GH link is more likely to be the most desired entry point by users of this site.
Note: I'm not the one who down-voted this.
Cassandra and Redis aren't really document databases. Cassandra is closer to BigTable as a column store, and Redis is more like an extended key/value store.
I'm generally skeptical of posts for "courses" on this and similar sites. In particular, at a glance, I don't know if this is a really free site, if some courses are free, or you can complete the lessons with or without payment. I don't have a problem with people wanting to get paid, but one really needs to be skeptical, there's a lot of junk.
Also, as MaxArt mentions, v5 is a few versions behind, but Angular had had far fewer breaking changes between versions since v3-4. The workflows are pretty solid.
I'm personally not a fan of Angular and prefer React+Redux+thunks/fetch myself YMMV but every time I've used or worked with Angular, I'm reminded of why I don't care for it.