Application Architecture with React: Rethinking Flux

Re:Application Architecture with React: Rethinking Flux by iLoch on Monday September 14, 2015 @11:46AM (#10215626)

Networking is a nearly trivial layer on top of the Flux pattern. I've found this especially true with Redux with the ability to easily wait on promises to mute state.

Meteor has its own problems too. The nice thing about Flux architecture is that you're not married to the network. Take my comparison with a grain of salt because I haven't given Meteor a try.

[ Parent | on HN ]

Re:Application Architecture with React: Rethinking Flux by tajano on Monday September 14, 2015 @02:24PM (#10216563)

Slightly off topic, but what library do you use for networking with React? Almost every code sample or tutorial uses jQuery's AJAX methods. Bundling jQuery seems excessive when just using those methods, but is there not a reliable alternative?

[ Parent | on HN ]

Re:Application Architecture with React: Rethinking Flux by sotojuan on Monday September 14, 2015 @06:42PM (#10217990)

There's tons, but the common one is fetch: https://github.com/matthew-andrews/isomorphic-fetch

[ Parent | on HN ]

Re:Application Architecture with React: Rethinking Flux by iLoch on Tuesday September 15, 2015 @08:24PM (#10223960)

Yeah I use fetch and a Redux React promise middleware module.

[ Parent | on HN ]